All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Chris Mason <mason@suse.com>, Jeff Mahoney <jeffm@suse.com>,
	Anders Widman <andewid@tnonline.net>,
	reiserfs-list@namesys.com
Subject: Re: Multiple data streams...
Date: Thu, 03 Apr 2003 22:37:24 +0400	[thread overview]
Message-ID: <3E8C7F64.8020008@namesys.com> (raw)
In-Reply-To: <16011.6694.600468.304009@laputa.namesys.com>

Nikita Danilov wrote:

>Chris Mason writes:
> > On Wed, 2003-04-02 at 11:53, Hans Reiser wrote:
> > > Users should know that these will never be accepted into ReiserFS, and 
> > > the reasons why are explained at www.namesys.com/v4/v4.html
> > 
> > They should also know that suse has committed to supporting the ACL and
> > xattr patches.  It's an important feature to our customers, so we more
> > or less had to choose between making something else the default and
> > giving reiserfs the features needed for it to compete in the enterprise
> > market.
> > 
> > We chose the latter ;-)
> > 
>
>Actually, locking ACLs out of mainline gives SuSe competitive advantage
>over, say, some other distribution that would like to use Reiserfs. In
>such situation that "other distribution" would probably opt for not
>using reiserfs at all.
>
>
> > -chris
> > 
>
>Nikita.
>
> > 
> > 
> > 
>
>
>
>  
>
and if we introduce a non-compatible version of ACLs into the mainline....

There are the Unix wannabes and those who want to build something 
better.  There aren't actually a lot who want to build something better 
than what has passed before.... but then there never is.....

Reiser4 is not going to adopt the wait until some other OS has used a 
feature for 5 years, and then adopt it approach that Ted Tso suggested 
on one occasion (I think we were discussing upcoming reiser4 features;-) ).

This is a natural friction between those who want Linux to quickly 
become like Unix, and those who think Unix is not necessarily all that 
we could be.  I suspect that as Linux matures this is going to become 
more and more of an issue, because those who are able to copy features 
effectively are not those who are able to add new ones, but those who 
copy will be entrenched in the power structure.  It will be much like 
the competition between slow growth and fast growth vegetation in the 
forest: both approaches have their place in the ecosystem and both seek 
to displace the other.

What we should all remember though is that everyone is trying to make 
Linux better as best as they can, and so let us not make a big deal out 
of this ACL fork because little positive will come out of it (please 
take note of this point Nikita).

-- 
Hans



  reply	other threads:[~2003-04-03 18:37 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
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 [this message]
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=3E8C7F64.8020008@namesys.com \
    --to=reiser@namesys.com \
    --cc=Nikita@Namesys.COM \
    --cc=andewid@tnonline.net \
    --cc=jeffm@suse.com \
    --cc=mason@suse.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.