From: Hank Leininger <linux-kernel@progressive-comp.com>
To: linux-kernel@vger.kernel.org
Subject: Re: symlink_prefix
Date: Mon, 4 Jun 2001 08:28:46 -0400 [thread overview]
Message-ID: <200106041228.IAA08746@mailer.progressive-comp.com> (raw)
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 :(
--
Hank Leininger <hlein@progressive-comp.com>
next reply other threads:[~2001-06-04 12:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 12:28 Hank Leininger [this message]
2001-06-05 2:31 ` symlink_prefix Ton Hospel
-- 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=200106041228.IAA08746@mailer.progressive-comp.com \
--to=linux-kernel@progressive-comp.com \
--cc=hlein@progressive-comp.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