From: Andries.Brouwer@cwi.nl
To: hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: Linux can use a mountpoint for 2 Filesystems
Date: Tue, 20 Nov 2001 19:41:33 GMT [thread overview]
Message-ID: <UTC200111201941.TAA317995.aeb@cwi.nl> (raw)
hpa:
> There are real reasons to overmount a filesystem. It's getting to be
> a usability problem, probably because Linux (UNLIKE MOST OTHER UNIXES)
> didn't allow it until just recently. This change caused some
> problems, including with the automount daemon. I would like to see an
> option to mount(8) to allow it, by default disallow by policy.
mount(8) does not necessarily have such information:
/etc/mtab is just a random file with random contents,
and /proc/mounts need not exist.
The cleanest way to do what you suggest would be to make the kernel
refuse an overmount unless the mount(2) flags included the
"overmount" flag.
Andries
next reply other threads:[~2001-11-20 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 19:41 Andries.Brouwer [this message]
2001-11-20 19:43 ` Linux can use a mountpoint for 2 Filesystems H. Peter Anvin
[not found] <Pine.LNX.4.10.10111191938450.12291-100000@master.linux-ide.org>
2001-11-20 3:46 ` Andre Hedrick
2001-11-20 4:50 ` H. Peter Anvin
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=UTC200111201941.TAA317995.aeb@cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=hpa@zytor.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox