From: Matthias Andree <ma+rfs@dt.e-technik.uni-dortmund.de>
To: linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: I oppose Chris and Jeff's patch to add an unnecessary additional namespace to ReiserFS
Date: Mon, 26 Apr 2004 22:40:37 +0200 [thread overview]
Message-ID: <20040426204037.GA21455@merlin.emma.line.org> (raw)
In-Reply-To: <1083006783.30344.102.camel@watt.suse.com>
On Mon, 26 Apr 2004, Chris Mason wrote:
> I hope v4 does improve the xattr api, and I hope it manages to do so for
> more then just reiser4. It is important that application writers are
> able to code to a single interface and get coverage across all the major
> linux filesystems.
Interesting point, given that SuSE were early adopters of alternative
file systems such as JFS, ReiserFS, and XFS (in lexicographical order
rather than order of appearance). These have always diversified the
semantics offered, not only in adding features that other systems didn't
have, but also in omitting features the other file systems did have -
chattr, for instance, or tail merging that confused boot loaders, for
another.
With respect to Hans's reasoning about name spaces, is there an official
standard that mandates a particular API for the ACL stuff ("POSIX")?
If so, the whole discussion is about getting out of the frying pan and
into the fire. The traditional approach will then be standards compliant
but be out-of-band and outside of the file system name space, the new
approach will be outside of the standards, requiring application
developers to produce a Linux and a POSIX version.
Or am I barking up the wrong tree?
--
Matthias Andree
Encrypt your mail: my GnuPG key ID is 0x052E7D95
next prev parent reply other threads:[~2004-04-26 20:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 19:54 [PATCH] reiserfs v3 patches for 2.6.6-rc2 Chris Mason
2004-04-26 16:59 ` I oppose Chris and Jeff's patch to add an unnecessary additional namespace to ReiserFS Hans Reiser
2004-04-26 17:31 ` Chris Mason
2004-04-26 18:15 ` Hans Reiser
2004-04-26 19:12 ` Mark Hahn
2004-04-26 19:13 ` Chris Mason
2004-04-26 20:40 ` Matthias Andree [this message]
2004-04-26 22:20 ` Chris Wright
2004-04-26 23:20 ` Andrew Morton
2004-04-27 17:35 ` Hans Reiser
2004-04-27 18:00 ` Markus Törnqvist
2004-04-26 19:33 ` Christoph Hellwig
2004-04-27 17:29 ` Hans Reiser
2004-04-27 17:34 ` Christoph Hellwig
2004-04-27 17:58 ` Hans Reiser
2004-04-27 18:04 ` Christoph Hellwig
2004-04-28 0:10 ` Stefan Traby
2004-04-27 18:07 ` Jeff Garzik
2004-04-28 5:51 ` Meelis Roos
2004-04-30 16:14 ` David Masover
2004-05-02 4:14 ` Rob Landley
2004-04-26 19:56 ` Matt H.
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=20040426204037.GA21455@merlin.emma.line.org \
--to=ma+rfs@dt.e-technik.uni-dortmund.de \
--cc=linux-kernel@vger.kernel.org \
--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 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®