From: Anthony <anthony@magix.com.sg>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Should mount --bind not follow symlinks?
Date: Tue, 13 Mar 2001 00:37:38 +0900 [thread overview]
Message-ID: <3AACED42.39DF0A24@magix.com.sg> (raw)
In-Reply-To: <Pine.GSO.4.21.0103120835390.25792-100000@weyl.math.psu.edu>
Alexander Viro wrote:
> Don't mix symlinks with mounts/bindings. Too much PITA and yes, it had
> been deliberately prohibited. You _really_ don't want to handle the
> broken symlinks and all the realted fun [...]
No. But I hoped _you_ might :-)
> - race-ridden at extreme and useless.
> In automount-like setups you can _replace_ symlinks with bindings.
> No need to mix them.
Hmm. My /etc/auto.opt contains
* :/export/opt/&/LATEST
where all the "LATEST"s etc are symlinks. I found it quite
an elegant way to maintain different versions: the symlink
was de-facto a trivially simple version database.
Does the version state now *have* to be listed in
/etc/auto.opt explicitly? That feels a little retrograde.
Perhaps I'm blissfully unaware of all sorts of vile
race conditions, but why can't the *automounter* chase
the symlinks even if mount shouldn't? Or am I missing
a neater solution?
Rgds
Anthony
next prev parent reply other threads:[~2001-03-12 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-12 10:44 Should mount --bind not follow symlinks? Anthony Heading
2001-03-12 13:40 ` Alexander Viro
2001-03-12 15:37 ` Anthony [this message]
2001-03-14 13:31 ` Jamie Lokier
2001-03-26 14:04 ` Anthony
2001-04-16 15:37 ` Kai Henningsen
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=3AACED42.39DF0A24@magix.com.sg \
--to=anthony@magix.com.sg \
--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;
as well as URLs for NNTP newsgroup(s).