On Wed, 18 Nov 2009, Karel Zak wrote: > The "flags" argument of mount(2) always contains MS_BIND for bind > mounts (if you use standard mount(8) command and /etc/mtab) for -o > remount. I think that's a bug. I can see the reasoning behind it, but it's wrong. mount(8) should not guess whether the user wants to change the per superblock flags or the per mount flags based on *how* the mount was created. Look: mount /dev/hda1 /mnt1; mount /dev/hda1 /mnt2 is completely equivalent to mount /dev/hda1 /mnt1; mount --bind /mnt1 /mnt2 Why should "mount -oremount" treat one differently than the other? It would be much cleaner to have a mount option, say --change-mnt-flags, that is equivalent to "--bind -oremount". Thanks, Miklos -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
