From: Peter Foldiak <Peter.Foldiak@st-andrews.ac.uk>
To: Rik van Riel <riel@redhat.com>
Cc: Peter Foldiak <Peter.Foldiak@st-andrews.ac.uk>,
Maciej Soltysiak <solt2@dns.toxicfilms.tv>,
Jesper Juhl <jesper.juhl@gmail.com>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
linux-kernel@vger.kernel.org, reiserfs-list@namesys.com,
Hans Reiser <reiser@namesys.com>
Subject: Re: creating live virtual files by concatenation
Date: Sat, 25 Feb 2006 23:23:36 +0000 [thread overview]
Message-ID: <4400E6F8.1080907@st-andrews.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.63.0602251736340.13659@cuia.boston.redhat.com>
Rik van Riel wrote:
>On Sat, 25 Feb 2006, Peter Foldiak wrote:
>
>>sub-file" corresponding to a key-range. Writing a chapter should change the
>>book that the chapter is part of. That is what would make it really valuable.
>>Of course it would have all sorts of implications (e.g. for metadata for each
>>part) that need to be thought about, but it could be done properly, I think.
>>
>>
>
>What happens if you read the first 10kB of a file,
>and one of the "chapters" behind your read cursor
>grows?
>
>Do you read part of the same data again when you
>continue reading?
>
>Does the read cursor automatically advance?
>
>
You should probably continue where you left off .
>Your idea changes the way userspace expects files
>to behave...
>
>
Yes, I know.
next prev parent reply other threads:[~2006-02-25 23:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-25 14:37 Maciej Soltysiak
2006-02-25 15:30 ` Jan Engelhardt
2006-02-27 19:52 ` Yoanis Gil Delgado
2006-02-25 15:35 ` Jesper Juhl
2006-02-25 17:15 ` Maciej Soltysiak
2006-02-25 18:40 ` Rik van Riel
2006-02-25 18:52 ` Jesper Juhl
2006-02-25 19:33 ` Re[2]: " Maciej Soltysiak
2006-02-25 22:30 ` Peter Foldiak
2006-02-25 22:38 ` Rik van Riel
2006-02-25 23:23 ` Peter Foldiak [this message]
2006-02-27 20:43 ` Hans Reiser
2006-02-27 20:39 ` Hans Reiser
2006-02-27 20:45 ` Jesper Juhl
2006-02-25 17:40 ` Peter Foldiak
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=4400E6F8.1080907@st-andrews.ac.uk \
--to=peter.foldiak@st-andrews.ac.uk \
--cc=jengelh@linux01.gwdg.de \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=riel@redhat.com \
--cc=solt2@dns.toxicfilms.tv \
/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
all inboxes | Powered by JetHome®