From: "Alexander G. M. Smith" <agmsmith@rogers.com>
To: reiserfs-list@namesys.com
Subject: Re: Multiple data streams...
Date: Wed, 02 Apr 2003 10:30:20 -0500 EST [thread overview]
Message-ID: <3134644043-BeMail@cr593174-a> (raw)
In-Reply-To: <200304022240.57346.russell@coker.com.au>
Russell Coker wrote on Wed, 2 Apr 2003 22:40:57 +1000:
> The Linux API does not support multiple data streams. Support for extended
> attributes has recently been added, this will do most things that you might
> want to do with multiple streams and does it in a standard way that is
> supported.
In case people don't know, extra streams are used extensively in BeOS (for icons, e-mail attributes (subject, sender, date, etc), MIME types of files
and lots of other things). Sometimes I wish their was a ReiserFS
implementation for BeOS so that performance would improve (small streams
are stored in the inode, but once that overflows, things get slow and
it uses at least two disk blocks for even the smallest stream data).
- Alex
next prev parent reply other threads:[~2003-04-02 15:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 9:28 Multiple data streams Anders Widman
2003-04-02 9:47 ` Anders Widman
2003-04-02 16:43 ` Hans Reiser
2003-04-03 16:49 ` Valdis.Kletnieks
2003-04-02 12:40 ` Russell Coker
2003-04-02 13:08 ` Anders Widman
2003-04-02 21:32 ` Russell Coker
2003-04-03 19:00 ` Hans Reiser
2003-04-03 19:57 ` Russell Coker
2003-04-03 21:53 ` Hans Reiser
2003-04-02 15:18 ` Oleg Drokin
2003-04-02 15:30 ` Alexander G. M. Smith [this message]
2003-04-02 16:12 ` Jeff Mahoney
2003-04-02 16:53 ` Hans Reiser
2003-04-02 17:07 ` Chris Mason
2003-04-02 17:13 ` Nikita Danilov
2003-04-03 18:37 ` Hans Reiser
2003-04-03 19:02 ` Chris Mason
2003-04-03 19:50 ` Hans Reiser
2003-04-03 20:09 ` Chris Mason
2003-04-04 7:41 ` Nikita Danilov
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=3134644043-BeMail@cr593174-a \
--to=agmsmith@rogers.com \
--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.