From: linux-kernel@ton.iguana.be (Ton Hospel)
To: linux-kernel@vger.kernel.org
Subject: Re: symlink_prefix
Date: Tue, 5 Jun 2001 02:31:56 +0000 (UTC) [thread overview]
Message-ID: <9fhgas$6pr$1@post.home.lunix> (raw)
In-Reply-To: <200106041228.IAA08746@mailer.progressive-comp.com>
In article <200106041228.IAA08746@mailer.progressive-comp.com>,
Hank Leininger <linux-kernel@progressive-comp.com> writes:
> On 2001-06-03, Andries.Brouwer@cwi.nl wrote:
>
>> Suppose I have devices /dev/a, /dev/b, /dev/c that contain the
>> /, /usr and /usr/spool filesystems for FOO OS. Now
>> mount /dev/a /mnt -o symlink_prefix=/mnt
>> mount /dev/b /mnt/usr -o symlink_prefix=/mnt
>> mount /dev/c /mnt/usr/spool -o symlink_prefix=/mnt
>
> Cool.
>
> What happens when someone creates new absolute symlinks under /mnt ?
> Will/should the magic /mnt/ header be stripped from any symlink created
> under such a path-translated volume? The answer is probably 'yes', but
> either one violates POLA :(
>
I think the semantics should be these that are used in the old usespace
nfsd for the "link_relative" option. That one had very intuitive semantics
and behaved sanely even if you had insane recursive machine crossmounts
next prev parent reply other threads:[~2001-06-05 2:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 12:28 symlink_prefix Hank Leininger
2001-06-05 2:31 ` Ton Hospel [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-03 17:37 symlink_prefix Andries.Brouwer
2001-06-03 16:36 symlink_prefix Andries.Brouwer
2001-06-03 17:19 ` symlink_prefix Alexander Viro
2001-06-04 22:05 ` symlink_prefix Albert D. Cahalan
2001-06-03 15:10 symlink_prefix Andries.Brouwer
2001-06-03 15:27 ` symlink_prefix Alexander Viro
2001-06-03 10:53 symlink_prefix Andries.Brouwer
2001-06-03 11:25 ` symlink_prefix Alexander Viro
2001-06-04 11:53 ` symlink_prefix Remi Turk
2001-06-05 12:43 ` symlink_prefix Pavel Machek
2001-06-07 1:00 ` symlink_prefix Edgar Toernig
2001-06-07 1:19 ` symlink_prefix Alexander Viro
2001-06-07 3:43 ` symlink_prefix Edgar Toernig
2001-06-02 23:54 symlink_prefix Andries.Brouwer
2001-06-03 0:23 ` symlink_prefix Robert Love
2001-06-03 0:49 ` symlink_prefix Alexander Viro
2001-06-03 1:00 ` symlink_prefix Mitchell Blank Jr
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='9fhgas$6pr$1@post.home.lunix' \
--to=linux-kernel@ton.iguana.be \
--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