From: Bernhard Voelker <mail@bernhard-voelker.de>
To: "util-linux@vger.kernel.org" <util-linux@vger.kernel.org>
Cc: "Pádraig Brady" <P@draigbrady.com>
Subject: mount.8: mtab as symlink
Date: Mon, 21 Jul 2014 08:05:29 +0200 [thread overview]
Message-ID: <53CCADA9.3020703@bernhard-voelker.de> (raw)
Hi Karel,
on coreutils' mailing list, we regularly receive complaints about
df(1) not working properly with bind mounts, and it turns out that
the users' system still has /etc/mtab as a regular file.
(There were recently a lot of attempts to fix issues with duplicate
mounts and over-mounting - and thus eclipsing - of source or target.)
Well, there might be a bug in df(1), anyway, we'd like to advise
the user to switch to mtab as a symlink to /proc/mounts or
/proc/self/mounts as it is common nowadays on many distros.
But then the user reads "man 8 mount" ...
It is possible to replace /etc/mtab by a symbolic link to
/proc/mounts, and especially when you have very large numbers
of mounts things will be much faster with that symlink, but some
information is lost that way, and in particular using the "user"
option will fail.
... and is scared about the last sentence.
Is this still true? I don't have problems with mounting "user"
file systems (apart from ntfs-3g) here. What are the problems,
and if they still exist, could the details be added to the man
page, please?
Thanks & have a nice day,
Berny
next reply other threads:[~2014-07-21 6:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 6:05 Bernhard Voelker [this message]
2014-07-21 8:28 ` mount.8: mtab as symlink Karel Zak
2014-07-21 21:16 ` Benno Schulenberg
2014-07-21 21:32 ` Bernhard Voelker
2014-07-21 22:18 ` Benno Schulenberg
2014-07-21 23:49 ` Karel Zak
2014-07-27 18:57 ` Benno Schulenberg
2014-07-29 10:21 ` Karel Zak
2014-07-29 19:41 ` helper= and uhelper= Benno Schulenberg
2014-07-30 7:26 ` Karel Zak
2014-07-31 19:47 ` Benno Schulenberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53CCADA9.3020703@bernhard-voelker.de \
--to=mail@bernhard-voelker.de \
--cc=P@draigbrady.com \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.