From: Christoph Hellwig <hch@infradead.org>
To: Hans Reiser <reiser@namesys.com>
Cc: Chris Mason <mason@suse.com>, Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org, reiserfs-list@namesys.com,
akpm@osdl.org
Subject: Re: I oppose Chris and Jeff's patch to add an unnecessary additional namespace to ReiserFS
Date: Mon, 26 Apr 2004 20:33:14 +0100 [thread overview]
Message-ID: <20040426203314.A6973@infradead.org> (raw)
In-Reply-To: <408D3FEE.1030603@namesys.com>; from reiser@namesys.com on Mon, Apr 26, 2004 at 09:59:26AM -0700
On Mon, Apr 26, 2004 at 09:59:26AM -0700, Hans Reiser wrote:
> The xattr namespace offers zero functional advantage over the file
> namespace. The use of '.' instead of '/' is idiotic, see the very short
> paper "The Hideous Name" by Rob Pike ( www.cs.bell-labs.com/cm/cs/doc/
> ) for why mindlessly varying the separators in hierarchical names
> throughout an OS is a bad idea.
Hans, where have you been the last three years? Hiding under a rock?
If Linux wants to support additional attributes and ACLs they better
have a common API for _all_ filesystems. People have discussed the xattr
issue to death, see the -fsdevel and acl-devel archives. I haven't
seen you input anywhere, so better shut up now.
If you don't want to suport xattrs and acls at all in your filesystem
that's your business, but adding random new APIs is not. If you want
your magic files included send them to -fsdevel, including how to
deal with them at the VFS level and using one set of entry points for
them and xattrs. If not keep on dreaming your pipe dreams and don't
anoy us with your 'research' fantasies.
As for ACLs in v3 that's a decision of the maintainer, currently you're
the formal maintainer, but I don't remember a single patch from you.
Most of the linux 2.6 work has been done by Chris and quite a bit of
work by your employees. Chris is paid for doing a stable and working
reiserfs variant for SuSE so he seems to be qualified for doing that, to..
next prev parent reply other threads:[~2004-04-26 19:33 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
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 [this message]
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=20040426203314.A6973@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=torvalds@osdl.org \
/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