From: Ion Badulescu <ionut@moisil.cs.columbia.edu>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH][CFT] per-process namespaces for Linux
Date: Wed, 28 Feb 2001 11:06:52 -0800 [thread overview]
Message-ID: <200102281906.f1SJ6qS02383@moisil.dev.hydraweb.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0102281302230.7107-100000@weyl.math.psu.edu>
On Wed, 28 Feb 2001 13:07:29 -0500 (EST), Alexander Viro <viro@math.psu.edu> wrote:
> On Wed, 28 Feb 2001, David L. Parsley wrote:
>> Yeah, mount --bind is cool, I've been using it on one of my projects
>> today. But - maybe I'm just not thinking creatively enough - what are
>> the advantages of mount --bind versus just symlinking?
>
> 1) Correctly working ".." (obviously relevant only for directories)
> 2) Try to create symlinks on read-only NFS mount. For bonus points, try
> to do that one one client without disturbing everybody else.
> 3) Try to make it different for different users, for that matter.
And disadvantages: you can't have broken symlinks.
This actually turns out to be quite a bit of a problem when one tries
to use bind mounts with autofs. For one thing, it's perfectly legal
to have /autofs/foo as a symlink to /autofs/bar/foo, where /autofs/bar
is not yet mounted -- but a bind mount can't handle that...
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
next prev parent reply other threads:[~2001-02-28 19:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-25 10:44 Manfred Spraul
2001-02-25 16:04 ` Alexander Viro
2001-02-25 19:01 ` Sandy Harris
2001-02-25 19:13 ` Alexander Viro
2001-02-25 21:57 ` Werner Almesberger
2001-02-25 22:39 ` Alexander Viro
2001-02-25 23:51 ` Werner Almesberger
2001-02-26 0:26 ` Alexander Viro
2001-02-26 11:54 ` Marco d'Itri
2001-02-26 12:51 ` Alexander Viro
2001-02-26 16:43 ` Alexander Viro
2001-02-27 20:08 ` Alexander Viro
2001-02-28 7:03 ` Albert D. Cahalan
2001-02-28 7:14 ` Alexander Viro
2001-02-28 18:13 ` David L. Parsley
2001-02-28 18:07 ` Alexander Viro
2001-02-28 19:06 ` Ion Badulescu [this message]
2001-02-28 19:18 ` Alexander Viro
2001-02-28 20:17 ` Ion Badulescu
2001-02-28 7:51 ` Alexander Viro
2001-02-25 19:48 ` Arjan van de Ven
2001-02-27 9:50 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-02-26 1:14 Andries.Brouwer
2001-02-26 1:39 ` Alexander Viro
2001-02-25 5:28 Rick Hohensee
2001-02-25 5:40 ` Alexander Viro
2001-02-25 4:16 Alexander Viro
2001-02-26 16:26 ` Peter J. Braam
2001-02-26 20:23 ` Christoph Hellwig
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=200102281906.f1SJ6qS02383@moisil.dev.hydraweb.com \
--to=ionut@moisil.cs.columbia.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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
all inboxes | Powered by JetHome®