From: Chris Mason <mason@suse.com>
To: "Alexander G. M. Smith" <agmsmith@rogers.com>
Cc: reiserfs-list@namesys.com
Subject: Re: using of XATTRs instead of pseudo files for accessing reiser4 file attributes.
Date: Tue, 06 Apr 2004 08:13:24 -0400 [thread overview]
Message-ID: <1081253603.4977.77.camel@watt.suse.com> (raw)
In-Reply-To: <38261445506-BeMail@cr593174-a>
On Mon, 2004-04-05 at 18:41, Alexander G. M. Smith wrote:
> Chris Mason wrote on Mon, 05 Apr 2004 08:46:26 -0400:
> > xattrs are the current linux api, you'll make it much easier for people
> > to use reiser4 by supporting it (in addition to whatever new and cool
> > API you develop).
>
> One of the big points is to cut down on the number of APIs and gain
> in saved effort. Listing attributes? Just use good old ReadDir().
> With a common name space, you can use grep and other well developed
> tools to deal with attributes. And so on.
Sure, I think namesys has some great ideas on the new pseudo files.
But, there are existing apps using the xattrs, it makes sense to get
them for a relatively small programming effort in reiser4 instead of
having to modify each one and get patches up stream.
-chris
next prev parent reply other threads:[~2004-04-06 12:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 11:54 using of XATTRs instead of pseudo files for accessing reiser4 file attributes Alex Zarochentsev
2004-04-05 12:46 ` Chris Mason
2004-04-05 22:41 ` Alexander G. M. Smith
2004-04-06 1:22 ` Hubert Chan
2004-04-06 12:13 ` Chris Mason [this message]
2004-04-07 7:55 ` using of XATTRs instead of pseudo files for accessing mjt
2004-04-05 15:55 ` using of XATTRs instead of pseudo files for accessing reiser4 file attributes Hans Reiser
2004-04-05 17:54 ` Narcoleptic Electron
2004-04-05 18:10 ` Alex Zarochentsev
2004-04-05 18:19 ` Alex Zarochentsev
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=1081253603.4977.77.camel@watt.suse.com \
--to=mason@suse.com \
--cc=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.