Re: mount: should -vf be handled by mount ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jul 25, 2007 at 08:21:55PM -0400, Mike Frysinger wrote:
> this isnt a regression from 2.12, just a bug report ;)
> 
> running:
> $ mount -nvf / -o remount
> does not exec any other programs and gives me nice output if the filesystem is 
> something simple like ext3 ... but if it's something like nfs or smbfs, the 
> sub mount program will be executed instead.  in the case of mount.nfs, no 

I've fixed mount.nfs in nfs-utils:

  commit f12ed63e95dec929d6893b16983233d2940a889c
  Author: Karel Zak <kzak@xxxxxxxxxx>
  Date:   Mon Mar 19 20:33:17 2007 +0100

     Correctly handle -f (fake) mount option.

     The fake option has to write to mtab like a normal mount. Read mount(8) man
     page for more details.  It's very important for system init scripts that use
     "-f" as a way how write info about mount points to /etc/mtab.

     Signed-off-by: Karel Zak <kzak@xxxxxxxxxx>
     Signed-off-by: Neil Brown <neilb@xxxxxxx>


No clue about mount.smbfs or others implementations (I think it's less
important than NFS -- probably nobody use SMB as a root filesystem).

> output is given (i can take that up with the nfs-utils guys) and in the case 
> of smbfs, mount.smbfs doesnt even understand these flags.
> 
> do these sub programs even need to be executed ?  is it done so that the 

We need the "mount.<type> -f" for systems where a <type> is a root
filesystem.

> option list is properly filled out ?

The syntax of external (u)mount helpers is described in mount.8 and
umount.8, but util-linux-ng-v2.13 is probably the first release where
this stuff is correctly implemented -- it means we need a time to fix
others mount.<type> (e.g. smbfs).

Don't think it's a critical problem.

Mike, it seems you use "mount -fnv / -o remount" as a replacement for
"mount | grep ^/" :-)

    Karel

-- 
 Karel Zak  <kzak@xxxxxxxxxx>
-
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux