On Mon, Nov 04, 2013 at 09:02:20AM -0500, Phillip Susi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> That is pretty much what I thought, but why is the bind flag stored
> when you do use mtab then? Shouldn't they give the same behavior, so
Historical reasons... 10 years ago nobody cares about the
sense of the flag in the mtab ;-(
And it's also difficult for userspace to generate the right mount
source device if a directory is specified.
I'm not sure if I want to change the mtab behavior if for example
old coreutils df(1) or some backup tools depend on this odd behavior.
It seems better to keep it without a change and provide a better
solution only for new systems without mtab.
> bind should not be stored in mtab? In particular it changes the way
> you have to remount a bind mount ro, which is an unexpected user
> visible change.
Yes. The update to systems without mtab has some disadvantages, but
it's still acceptable compare to mtab disadvantages.
Fedora did the change years (2?) ago and the number of the bug
reports related to this problem is almost zero. The question is what
will happen on server (e.g. RHEL), we will see :-)
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
