From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux can use a mountpoint for 2 Filesystems
Date: 19 Nov 2001 20:50:56 -0800 [thread overview]
Message-ID: <9tcnfg$57m$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10111191938450.12291-100000@master.linux-ide.org> <Pine.LNX.4.10.10111191939290.12141-100000@master.linux-ide.org>
Followup to: <Pine.LNX.4.10.10111191939290.12141-100000@master.linux-ide.org>
By author: Andre Hedrick <andre@linux-ide.org>
In newsgroup: linux.dev.kernel
>
> Greetings Gernot,
>
> You can do this with all real and virtual spindles under Linux.
> The reality is total crap that it can happen, but what the hey ...
> No policies in UNIX, ROOT beware.
>
> Sorry, but this report saddens me, issues like these are permitted
> There are no kernel controls to prevent multi mounting to the same point.
>
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.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2001-11-20 4:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10111191938450.12291-100000@master.linux-ide.org>
2001-11-20 3:46 ` Linux can use a mountpoint for 2 Filesystems Andre Hedrick
2001-11-20 4:50 ` H. Peter Anvin [this message]
2001-11-20 19:41 Andries.Brouwer
2001-11-20 19:43 ` 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='9tcnfg$57m$1@cesium.transmeta.com' \
--to=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 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.