From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jamie Lokier Subject: Re: Fallthrus as full-length symlinks? Date: Tue, 17 Nov 2009 06:44:00 +0000 Message-ID: <20091117064400.GB19996@shareable.org> References: <62b7cf460911151915k12c57c6dne9b49399bd8ce9d5@mail.gmail.com> <62b7cf460911161657i2c9ca63cv5e4fa65b514593b@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org To: AYAN TYAGI Return-path: Received: from mail2.shareable.org ([80.68.89.115]:34618 "EHLO mail2.shareable.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752447AbZKQGnz (ORCPT ); Tue, 17 Nov 2009 01:43:55 -0500 Content-Disposition: inline In-Reply-To: <62b7cf460911161657i2c9ca63cv5e4fa65b514593b@mail.gmail.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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