From: Jamie Lokier <jamie@shareable.org>
To: AYAN TYAGI <ayan.tyagi@gmail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Fallthrus as full-length symlinks?
Date: Tue, 17 Nov 2009 06:44:00 +0000 [thread overview]
Message-ID: <20091117064400.GB19996@shareable.org> (raw)
In-Reply-To: <62b7cf460911161657i2c9ca63cv5e4fa65b514593b@mail.gmail.com>
AYAN TYAGI wrote:
> > >Another idea that I first had when reading the suggestion was to use a
> > >symlink to self (ln -s x x) as the encoding for a fallthrough. It does
> > >not allow renames like what you really describe, but it has another advantage
> > >in that it does not require extensions to the upper file system layout
> > >while not conflicting with any use case I can see.
>
> It seems to be a great idea to make use of self referenced symlinks .
> Could you please describe the whole process u are proposing?
>
> If possible give some example and code .
That'll do surprising things when the user _really_ makes a
self-referencing symlink with "ln -s x x", which can happen
unexpectedly, for example by untarring some archive.
If a fallthrough is encoded that way, there should probably be an
error when the user tries to make a self-referencing symlink.
-- Jamie
next prev parent reply other threads:[~2009-11-17 6:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <62b7cf460911151915k12c57c6dne9b49399bd8ce9d5@mail.gmail.com>
2009-11-17 0:57 ` Fallthrus as full-length symlinks? AYAN TYAGI
2009-11-17 6:44 ` Jamie Lokier [this message]
2009-11-17 8:03 ` AYAN TYAGI
2009-11-17 19:47 ` Valerie Aurora
2009-11-13 17:46 Valerie Aurora
2009-11-13 18:46 ` Erez Zadok
2009-11-13 19:55 ` Arnd Bergmann
2009-11-17 19:06 ` Valerie Aurora
2009-11-17 19:13 ` Valerie Aurora
2009-11-17 19:18 ` David Woodhouse
2009-11-17 19:43 ` Valerie Aurora
2009-11-17 20:20 ` Erez Zadok
2009-11-23 18:26 ` Valerie Aurora
2009-11-23 18:44 ` Arnd Bergmann
2009-11-25 2:12 ` Valerie Aurora
2009-11-24 11:18 ` Miklos Szeredi
2009-11-18 5:47 ` hooanon05
2009-11-25 2:15 ` Valerie Aurora
2009-11-25 2:36 ` hooanon05
2009-11-25 9:43 ` David Woodhouse
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=20091117064400.GB19996@shareable.org \
--to=jamie@shareable.org \
--cc=ayan.tyagi@gmail.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;
as well as URLs for NNTP newsgroup(s).