From: Hans Reiser <reiser@namesys.com>
To: Russell Coker <russell@coker.com.au>
Cc: Anders Widman <andewid@tnonline.net>, reiserfs-list@namesys.com
Subject: Re: Multiple data streams...
Date: Thu, 03 Apr 2003 23:00:41 +0400 [thread overview]
Message-ID: <3E8C84D9.3000401@namesys.com> (raw)
In-Reply-To: <200304030732.31133.russell@coker.com.au>
Russell Coker wrote:
>On Wed, 2 Apr 2003 23:08, Anders Widman wrote:
>
>
>>>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.
>>>
>>>
>> Could you give an example of this? I use multiple streams for adding
>> thumbnails or text files to pictures I am working on... - just to
>> give an example.
>>
>>
>
>OS/2 used EA's for icons and description text in 1992. There's no reason why
>EAs can't be used for this purpose today as well.
>
>
>
Implement inherited stat data, hidden directory entries, and files and
directories and you don't need EAs.... yes?
--
Hans
next prev parent reply other threads:[~2003-04-03 19:00 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 [this message]
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
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=3E8C84D9.3000401@namesys.com \
--to=reiser@namesys.com \
--cc=andewid@tnonline.net \
--cc=reiserfs-list@namesys.com \
--cc=russell@coker.com.au \
/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.