From: Al Viro <viro@ZenIV.linux.org.uk>
To: Joerg Schilling <schily@schily.net>
Cc: jack@suse.cz, otnaccess@hotmail.com,
linux-fsdevel@vger.kernel.org, joerg@schily.net
Subject: Re: FW: Symbolic link with absolute target path in UDF - not working properly?
Date: Tue, 13 Dec 2011 20:26:53 +0000 [thread overview]
Message-ID: <20111213202653.GJ2203@ZenIV.linux.org.uk> (raw)
In-Reply-To: <4ee7ad60.v6cTrJDUPPEjdDhI%schily@schily.net>
On Tue, Dec 13, 2011 at 08:54:08PM +0100, Joerg Schilling wrote:
> Please reread my previous mail. Your problem is that you use the wrong linux
> nomenclature while reading my text.
>
> The pointer to the related "lofs" sourcecode explains how it works and why it
> works as expected on Solaris.
>
> Note that a mount point relative absolute path needs to be evaluated against
> the real original (first) mount and not against the second loopback mount.
Except that unlike your lofs, bindings are symmetrical. I.e. there is no
such thing as "real" mount - they are simply mounts refering to various
subtrees of given fs. And mount --bind /foo/bar /baz does *not* render /foo
impossible to umount. Not to mention that even on Solaris there's such
thing as chroot and you really don't want to open that can of worms...
next prev parent reply other threads:[~2011-12-13 20:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SNT126-DS19FDA9F050C2D5E43731CDBEB40@phx.gbl>
2011-12-07 18:06 ` FW: Symbolic link with absolute target path in UDF - not working properly? Jan Kara
[not found] ` <SNT126-DS1C6361C26AD146EBA3BB6BEBE0@phx.gbl>
2011-12-12 14:18 ` Jan Kara
[not found] ` <SNT126-DS114F372B3DA7DF425B8146BEBC0@phx.gbl>
2011-12-13 11:01 ` Joerg Schilling
2011-12-13 16:13 ` Jan Kara
2011-12-13 18:30 ` Joerg Schilling
2011-12-13 19:25 ` Jan Kara
2011-12-13 19:54 ` Joerg Schilling
2011-12-13 20:26 ` Al Viro [this message]
2011-12-13 22:41 ` Joerg Schilling
2011-12-14 0:45 ` Al Viro
2011-12-14 17:34 ` Joerg Schilling
2011-12-13 20:05 ` Al Viro
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=20111213202653.GJ2203@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=jack@suse.cz \
--cc=joerg@schily.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=otnaccess@hotmail.com \
--cc=schily@schily.net \
/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).