From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hans Reiser Subject: Re: file as a directory Date: Tue, 14 Dec 2004 21:19:32 -0800 Message-ID: <41BFC964.2070301@namesys.com> References: <200411301631.iAUGVT8h007823@laptop11.inf.utfsm.cl> <41ACA7C9.1070001@namesys.com> <1103043518.21728.159.camel@pear.st-and.ac.uk> <41BF21BC.1020809@namesys.com> <1103059622.2999.17.camel@grape.st-and.ac.uk> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <1103059622.2999.17.camel@grape.st-and.ac.uk> List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Peter Foldiak Cc: reiserfs-list@namesys.com, linux-kernel@vger.kernel.org Peter Foldiak wrote: >On Tue, 2004-12-14 at 17:24, Hans Reiser wrote: > > >>Peter, I think you are right, though it might be useful to have the >>default be dirname/..../glued and to allow users to link >>dirname/..../filebody to >>dirname/..../something_else_if_they_want_it_to_not_be_glued, and to have >>dirname/..../filebody or whatever it is linked to be what they get if >>they read the directory as a file. >> >> > >Yes. I assume you mean that dirname in itself should always be >interpreted as dirname/..../glued, which by default would be a linked to >dirname/..../filebody, the latter being the file content, right? > > reversed: dirname in itself should always be interpreted as dirname/..../filebody, which by default would be a linked to dirname/..../glued, >Also, a pseudofile (e.g. dirname/..../structure ?) could be used to >specify how the files should be glued together. A simple question is, >for instance, what separators to use between the components, and what >ordering to use when putting the component objects together. (This >pseudofile could also determine more complicated ways of composing >objects.) > > Could be cool. >The component objects themselves could be full objects, so they >themselves could have sub-components. > Peter > > > > >