From: Hans Reiser <reiser@namesys.com>
To: Peter Foldiak <Peter.Foldiak@st-andrews.ac.uk>
Cc: reiserfs-list@namesys.com
Subject: Re: Interview with Hans on KernelTrap
Date: Thu, 15 Sep 2005 09:20:39 -0700 [thread overview]
Message-ID: <43299F57.4080008@namesys.com> (raw)
In-Reply-To: <43292AA8.1050304@st-andrews.ac.uk>
Peter Foldiak wrote:
> Hans Reiser wrote:
>
>>> 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.
>>
>>
> Sure, you can have only one "default" behaviour. (For instance, you
> would also need some metafiles to specify the details of how exactly
> the concatenation should be done, (e.g. what ordering (or structure)
> to use, whether to put something in between the files, etc.) in
> addition to all the other ones.) Peter
>
>
Yes, true.
next prev parent reply other threads:[~2005-09-15 16:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 17:01 Interview with Hans on KernelTrap Hubert Chan
2005-09-14 13:08 ` Peter Foldiak
2005-09-14 14:11 ` Yiannis Mavroukakis
2005-09-14 14:59 ` Bruce Israel
2005-09-14 15:20 ` Peter Foldiak
2005-09-14 19:59 ` Hans Reiser
2005-09-15 8:02 ` Peter Foldiak
2005-09-15 16:20 ` Hans Reiser [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-16 10:24 Tomasz Chmielewski
2005-09-16 15:38 ` Tom Vier
2005-09-16 16:19 ` Edward Shishkin
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=43299F57.4080008@namesys.com \
--to=reiser@namesys.com \
--cc=Peter.Foldiak@st-andrews.ac.uk \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.