From: Robert Love <rml@tech9.net>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org, viro@math.psu.edu
Subject: Re: symlink_prefix
Date: 02 Jun 2001 20:23:25 -0400 [thread overview]
Message-ID: <991527807.771.4.camel@phantasy> (raw)
In-Reply-To: <UTC200106022354.BAA182685.aeb@vlet.cwi.nl>
In-Reply-To: <UTC200106022354.BAA182685.aeb@vlet.cwi.nl>
On 03 Jun 2001 01:54:43 +0200, Andries.Brouwer@cwi.nl wrote:
> This evening I needed to work on a filesystem of a non-Linux OS,
> full of absolute symlinks. After mounting the fs on /mnt, each
> symlink pointing to /foo/bar in that filesystem should be
> regarded as pointing to /mnt/foo/bar.
>
> Since doing ls -ld on every component of every pathname was
> far too slow, I made a small kernel wart, where a mount option
> -o symlink_prefix=/pathname would cause /pathname to be prepended
> in front of every absolute symlink in the given filesystem
> (when the symlink is followed). That works satisfactorily.<snip>
unfortunately i cant speak for whether or not this patch is
reengineering the work of altroot (i have no experience with it) or
whether there are other similar approaches.
what i can say is that this is an excellent idea -- i have often cursed
having absolute symlinsk v. relative ones and this option would provide
a wonderful fix to that.
plus, i bet this is a rather simple and clean option.
i would like to see this in the kernel if it does not tread on any other
similar feature.
> (i) is there already a mechanism that would achieve this?
cant answer
> (ii) if not, do we want something like this in the kernel?
for sure.
--
Robert M. Love
rml@ufl.edu
rml@tech9.net
next prev parent reply other threads:[~2001-06-03 0:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-02 23:54 symlink_prefix Andries.Brouwer
2001-06-03 0:23 ` Robert Love [this message]
2001-06-03 0:49 ` symlink_prefix Alexander Viro
2001-06-03 1:00 ` symlink_prefix Mitchell Blank Jr
-- strict thread matches above, loose matches on Subject: below --
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-03 15:10 symlink_prefix Andries.Brouwer
2001-06-03 15:27 ` symlink_prefix Alexander Viro
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 17:37 symlink_prefix Andries.Brouwer
2001-06-04 12:28 symlink_prefix Hank Leininger
2001-06-05 2:31 ` symlink_prefix Ton Hospel
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=991527807.771.4.camel@phantasy \
--to=rml@tech9.net \
--cc=Andries.Brouwer@cwi.nl \
--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