All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Perkel <marc@perkel.com>
To: reiserfs-list@namesys.com
Subject: Re: Reiser4 and ACLs
Date: Sun, 14 Aug 2005 06:41:48 -0700	[thread overview]
Message-ID: <42FF4A1C.9030406@perkel.com> (raw)
In-Reply-To: <17151.17921.996376.693013@gargle.gargle.HOWL>



Nikita Danilov wrote:

>Not exactly. As a matter of fact, ACL and EA support was already
>implemented in reiser4. But it used standard xattrs API to interface to
>the user-land, and it was decided that reiser4 should go sys_reiser4()
>route instead. So, it was reaped.
>
>Nikita.
>  
>

OK - now I'm confused. Why not the standard? After all - it is standard. 
And - when is this going to be included?

My background is in Netware. Netware did it right. It's permissions that 
it had 15 years ago were beyond what Linux might ever acheive. Then I 
downgraded to Windows, then I further downgraded to Linux. In fact when 
I started using linux it took me months of denial before I realized - 
this really is all there is. One user, one group - and that's all. 
Further - the ability of a user to delete files that they have no 
read/write rights to is just plain silly. In Netware if you have no 
right to a file, you not only can't delete it - you can't even list it 
in the directory. It's as if that file isn't even there.

ACLs finally restored some of this power although the implementation in 
Linux is crude at best. I thought there is a glimmer of hope that some 
day Linux will catch up to where Novell was 15 years ago. It is so 
frustrating dealing with Linux culture and VI mentality trying to get 
people to think outside the box.


-- 
Marc Perkel - marc@perkel.com

Spam Filter: http://www.junkemailfilter.com
    My Blog: http://marc.perkel.com


  reply	other threads:[~2005-08-14 13:41 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 [this message]
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
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=42FF4A1C.9030406@perkel.com \
    --to=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.