public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Hans Reiser <reiser@namesys.com>
Cc: 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 13:31:52 -0400	[thread overview]
Message-ID: <1083000711.30344.44.camel@watt.suse.com> (raw)
In-Reply-To: <408D3FEE.1030603@namesys.com>

On Mon, 2004-04-26 at 12:59, Hans Reiser wrote:

> In the free software community you have to produce working code to be 
> paid attention to.  We are doing that.  Chris is sending his patch in at 
> this time in part because V4 is about to make his work completely 
> obsolete.  

We write patches for v3 because that is what our users are using.  We
write patches to support xattrs because those are the interfaces that
linux as a whole supports.  

v4 didn't factor into these decisions because it was still in extremely
early stages back then (2.4.16 or so).

I welcome v4, it has a lot of improvements over v3 and I very much want
to see v4 (and namesys) succeed.

> I also view 
> V3 as stable code that should not be disturbed more than minimally 
> necessary, and I desire for all new functionality to go into V4 (Chris 
> was also told that before his patch was written).
> 

You can't release v4 and then expect all the v3 users to disappear
instantly.  Our users have an expectation that the filesystem they
choose for their production systems will be reasonably maintained over
time.

I consider supporting the linux standard interfaces for acls and xattrs
part of being reasonably maintained, and the pending release of v4
doesn't change that.

> Making it possible to unify operating system namespaces was why ReiserFS 
> was created.  I am not in this for the money.  Pasting in an additional 
> namespace beyond what Unix had for short term marketing reasons violates 
> its soul, and I have no desire to provide support for it as it 
> complicates one feature at a time over 30 years.
> 
Disliking the xattr interface is a different discussion.  We
specifically did not do new and interesting namespace research with the
v3 patches, we supported the existing apis in as plain and non-intrusive
a manner possible.

These patches were not a quick hack, a lot of thought went into making
them usable in existing v3 installations, and they have been around for
quite a while.

-chris



  reply	other threads:[~2004-04-26 17:32 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 [this message]
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
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=1083000711.30344.44.camel@watt.suse.com \
    --to=mason@suse.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --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