From mboxrd@z Thu Jan  1 00:00:00 1970
From: Hans Reiser <reiser@namesys.com>
Subject: Re: Interview with Hans on KernelTrap
Date: Wed, 14 Sep 2005 12:59:21 -0700
Message-ID: <43288119.9000605@namesys.com>
References: <878xy0sy0d.fsf@evinrude.uhoreg.ca> <432820E8.9080201@st-andrews.ac.uk>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <reiserfs-list-return-25959-reiserfs=m.gmane.org@namesys.com>
list-help: <mailto:reiserfs-list-help@namesys.com>
list-unsubscribe: <mailto:reiserfs-list-unsubscribe@namesys.com>
list-post: <mailto:reiserfs-list@namesys.com>
Errors-To: flx@namesys.com
In-Reply-To: <432820E8.9080201@st-andrews.ac.uk>
List-Id: <reiserfs-devel.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: Peter Foldiak <Peter.Foldiak@st-andrews.ac.uk>
Cc: reiserfs-list@namesys.com

Peter Foldiak wrote:

> Hans, in the interview you give the example:
>
>  cat /home/reiser/mp3s/..../childcat > /dev/dsp
>
> to illustrate concatenation.
>
> I sorry for repeating myself, but still think it would be a lot cooler
> to be able to simply do:
>
>  cat /home/reiser/mp3s > /dev/dsp
>
> to achieve the same effect.

True.

> (We had a discussion of this (as part of the huge "file as directory"
> thread on the lists)
> http://www.ussg.iu.edu/hypermail/linux/kernel/0411.3/0044.html
> http://www.ussg.iu.edu/hypermail/linux/kernel/0505.1/0365.html
> and you seemed to agree then
> http://www.ussg.iu.edu/hypermail/linux/kernel/0505.1/0423.html
> )
> The convention (I think also approved(suggested?) by Linus at some
> point) could be that where you say
>
>  /home/reiser/mp3s
>
> you get a the file (or concatenation, if the directory has no "file"
> content itself), but when you say
>
>  /home/reiser/mp3s/
>
> (with the trailing "/"), you get the directory.
>
> So
>  book/chapter3/paragraph2
> is the second paragraph of the third chapter
> (or even better, a la XPath:
>  book/chapter[3]/paragraph[2]
> )
>
>  book/chapter3
> is the chapter
>
>  book
> is the whole book.
>
> The user (or tools) don't even have to know which is the "real" file,
> which are "parts of real files" and which are "concatenations of real
> files". This is really good for namespace unification across
> part-whole hierarchies. If you are required to use /..../ in the
> middle, it breaks this I think. Could we get rid of requiring "...."
> in the middle? (Would that break too much?)    Peter
>
In this specific instance, yes, but other pseudofiles would still need it.

My example was not a good one, I should have found a better one, sorry
for that.

>
>