From: vine24683579@gmail.com   
      
   On Monday, 20 February 2023 at 05:01:49 UTC, Mike Spencer wrote:   
   [snip]   
   > There seems to be two questions:   
   >   
   > 1. Why do some 15.0 installs have mtab a file and others a symlink?   
   > Related: What/where is the code that makes the symlink and what   
   > happened to it if there *is* no symlink?   
   >   
   > Different people put together the 32 and 64 bit packages?   
   > Oversight? Complexity catastrophy? :-) No real clue.   
      
   All new installs using the slackware-15.0/slackware-current installer   
   will have /etc/mtab as a symlink.  If instead you continuously upgrade   
   slackware-current pre-2018 to post-2018 without using the installer,   
   having /etc/mtab as a file should be preserved - see rc.S.   
      
   What this in turn means is that if you delete the symlink and do 'touch   
   /etc/mtab' and reboot, mount should restablish /etc/mtab as a file   
   for you.  In which case a user umount on your nfs mount should work   
   again.  Try it and see.  However since this is an infrequently used   
   approach it is possible something else may not work correctly.   
      
   > 2. Given that mtab is a symlink, why doesn't umount work for   
   > user-mouted NFS mounts?   
      
   This question has already been answered.  /proc/self/mounts   
   contains different information from what /etc/mtab would contain.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)