All of lore.kernel.org
 help / color / mirror / Atom feed
From: michael chang <thenewme91@gmail.com>
To: Marc Perkel <marc@perkel.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Reiser4 and ACLs
Date: Mon, 15 Aug 2005 19:37:03 -0400	[thread overview]
Message-ID: <b14e81f00508151637be3d229@mail.gmail.com> (raw)
In-Reply-To: <43012598.7080207@perkel.com>

On 8/15/05, Marc Perkel <marc@perkel.com> wrote:
> It seems to me that getting in the Kernel is the most important thing.

This is because nothing else can happen because no one will know it
exists.  Everything else will happen *as soon as* Reiser4 gets in. 
Otherwise, it's practically useless.

> Then getting it compatible with existing standards. Then you build up

But then you're basically rewriting ext2 or 3.  There's no point in that.

> the user based (addicts) and then you add the innovative stuff.

You do this first, because it's what sets you appart.  Otherwise,
people won't convert away from EXT2/3.  Priorities first.

> Otherwise people are going to use Ext3 because it has ACLs and Reiser4
> doesn't. That's where I'm at. If it doesn't do ACLs it doesn't work. I
> need acls.

So why fix something that isn't broken?  Just because one person who
uses ACLs doesn't use Reiser4 right away doesn't mean he won't use it
later.  Compare the number of people who use Ubuntu Linux (who won't
support Reiser4 until it's vanilla) and other Vanilla kernels, to the
number of ACL users.  The numbers matter.

> The way I see it - and I may well be missing something - s that the
> current API is just a way of talking to the security layer. So why not
> support multiple ways to talk to it?

There is nothing wrong with this idea.  It's just time consuming. 
It's not done, yet (for Reiser4).  If someone is willing to pay the
time/sweat or the money to get it done, it will be done.  Otherwise,
it won't.  Simple as that.

-- 
~Mike
 - Just my two cents
 - No man is an island, and no man is unable.

  reply	other threads:[~2005-08-15 23:37 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
2005-08-15 23:30                     ` Marc Perkel
2005-08-15 23:37                       ` michael chang [this message]
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=b14e81f00508151637be3d229@mail.gmail.com \
    --to=thenewme91@gmail.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.