All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Masover <ninja@slaphack.com>
To: Marc Perkel <marc@perkel.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Reiser4 and ACLs
Date: Mon, 15 Aug 2005 18:24:48 -0500	[thread overview]
Message-ID: <43012440.8020804@slaphack.com> (raw)
In-Reply-To: <43010157.1030107@perkel.com>

Marc Perkel wrote:
> 
> 
> Nikita Danilov wrote:
> 
>>
>> Well, this song has been sung many times already. :-) Hans has strong
>> opinion about xattr API (which, indeed, is not a paragon of design
>> beauty by a large margin).
>>  
>>
> I'm new to this debate. What is his strong opinion?

Well, I'll let him speak for himself, but I think it's basically this:

xattrs suck, for reasons which are varied and irrelevant.

When it's done, the sys_reiser4 api (and file-as-dir/metas/whatever) 
will be able to do everything xattrs did, only much better, faster, and 
more powerfully.

So, it's more worth their time to work on other things, like:
- kernel acceptance
- repacker
- crypto/compression
- security ("views" or ACLs)

Of course, if someone wanted to pay them for xattrs, and they didn't 
have another contract going, they'd probably support xattrs.  But for 
now, it's probably up to us to add xattr support.

Once it's added, these should do the same thing:

openat ("some_attribute")
open ("metas/some_attribute")
// or maybe
open ("metas/xattrs/some_attribute")

Well, there's more to it than that, but the most important thing is, the 
xattrs should be a subset of the metas namespace.


  reply	other threads:[~2005-08-15 23:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-14  4:34 Reiser4 and ACLs Marc Perkel
2005-08-14  8:08 ` Mark Nipper
2005-08-14 12:26   ` Marc Perkel
2005-08-14 12:31     ` michael chang
2005-08-14 12:38       ` Marc Perkel
2005-08-14 15:44         ` Valdis.Kletnieks
2005-08-14 13:24       ` Nikita Danilov
2005-08-14 13:41         ` Marc Perkel
2005-08-14 17:44           ` Matt Stegman
2005-08-14 19:52           ` David Masover
2005-08-15 17:08         ` Hubert Chan
2005-08-15 20:19           ` Nikita Danilov
2005-08-15 20:34             ` Jonathan Briggs
2005-08-15 20:44               ` Nikita Danilov
2005-08-15 20:55                 ` Marc Perkel
2005-08-15 23:24                   ` David Masover [this message]
2005-08-15 23:30                     ` Marc Perkel
2005-08-15 23:37                       ` michael chang
2005-08-16  0:21                         ` David Masover
2005-08-16  1:26                       ` Hubert Chan
2005-08-16 14:12                         ` michael chang
2005-08-15 23:28               ` David Masover
2005-08-15 20:52             ` Marc Perkel
2005-08-15 23:25               ` David Masover
2005-08-14 19:55     ` David Masover
  -- strict thread matches above, loose matches on Subject: below --
2005-08-17 14:10 Marc Perkel
2005-08-17 19:06 ` Hans Reiser

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=43012440.8020804@slaphack.com \
    --to=ninja@slaphack.com \
    --cc=marc@perkel.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.