From: Florin Malita <mali@go.ro>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Mountpoint lookup
Date: 06 Feb 2003 12:39:43 +0200 [thread overview]
Message-ID: <1044523812.1341.48.camel@zed.malinux.net> (raw)
In-Reply-To: <OF022E94CD.FEB25CC4-ON87256CC4.007381FC-88256CC4.0074BAF1@us.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
On Wed, 2003-02-05 at 23:15, Bryan Henderson wrote:
> To the extent that this translation would be handy, it would be appropriate
> to pass the information as a filesystem-type-specific mount parameter
> (which is actually a parameter of the filesystem image, not of the mount),
> but the semantics of the parameter wouldn't be "this is the mount point,"
> but rather "translate absolute symlinks with respect to this base path."
> You could have a mount program that automatically sets this parameter to
> the same path as the mount point, but of course you'd still have to have a
> lot of disclaimers that imported absolute symlinks don't always work the
> way the user expects.
Sounds reasonable.
But how about translating all remote absolute symlinks to relative ones?
Seems to be quite easy and eliminates any need of mount point knowledge.
--
Florin Malita web: http://www.malinux.net
public key: http://www.malinux.net/data/fmalita.gpg
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-02-06 10:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 15:02 Mountpoint lookup Florin Malita
2003-02-05 15:03 ` Christoph Hellwig
[not found] ` <1044459408.23735.147.camel@zed.malinux.net>
[not found] ` <20030205154536.A21838@infradead.org>
2003-02-05 20:03 ` Florin Malita
2003-02-05 21:15 ` Bryan Henderson
2003-02-06 10:39 ` Florin Malita [this message]
2003-02-22 18:56 ` David Chow
2003-02-05 19:13 ` Andrew Sharp
2003-02-05 19:18 ` Christoph Hellwig
2003-02-05 20:06 ` Bryan Henderson
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=1044523812.1341.48.camel@zed.malinux.net \
--to=mali@go.ro \
--cc=hbryan@us.ibm.com \
--cc=linux-fsdevel@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