From: Chris Mason <mason@suse.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Nikita Danilov <Nikita@Namesys.COM>,
Jeff Mahoney <jeffm@suse.com>,
Anders Widman <andewid@tnonline.net>,
reiserfs-list@namesys.com
Subject: Re: Multiple data streams...
Date: 03 Apr 2003 14:02:39 -0500 [thread overview]
Message-ID: <1049396559.15217.1127.camel@tiny.suse.com> (raw)
In-Reply-To: <3E8C7F64.8020008@namesys.com>
On Thu, 2003-04-03 at 13:37, Hans Reiser wrote:
> and if we introduce a non-compatible version of ACLs into the mainline....
>
Grin, the sentence above is more than a little fuzzy. The v3 ACLs in
the suse kernel are compatible with the acl standards used by the other
linux filesystems. Any acls in v4 probably want to provide the same
interface, given that many applications in linux do or will support it.
> 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.....
>
Shrug, acls as they are is better than no acls. It's great that you
want to enhance and extend filesystems, their interfaces and performance
over all. But while that is going on we need to make sure reiserfs
keeps up with the important features the other linux filesystems are
already including.
> 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).
I've no desire to create friction with the ACL fork at all ;-) It's a
relatively small change that adds a cool feature without altering the
disk format, in other words it was designed to be non-intrusive.
I know that you were concerned about the v3 acl support being a
compatibility problem in v4, but given the acls/xattrs can easily be
exported to a neutral format and then reimported into whatever v4
supports, I don't think it will be a problem. If it is, we'll work with
you to help fix it.
But none of that is the crucial issue ;-) Your previous message implied
the v3 acl patch was dead and I wanted to assure the people SuSE has
sold it to that we will continue to support it (and them).
-chris
next prev parent reply other threads:[~2003-04-03 19:02 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
2003-04-03 19:02 ` Chris Mason [this message]
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=1049396559.15217.1127.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=Nikita@Namesys.COM \
--cc=andewid@tnonline.net \
--cc=jeffm@suse.com \
--cc=reiser@namesys.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.