From: pelletierma@netscape.net
To: linux-kernel@vger.kernel.org
Subject: Re: ACL support
Date: Thu, 07 Mar 2002 15:58:43 -0500 [thread overview]
Message-ID: <3EA14851.578E6D9E.5016AB90@netscape.net> (raw)
Hello.
In response to a number of email I have received, I wanted to make
something clear: I'm not out to compete with the bestbit implementation of
ACLs over extended file attributes. :-)
What I am offering is an alternative implementation of ACL support at the
VFS level, that remains independent of filesystem support for ACLs. In
fact, my patch provides filesystem support for ramfs only at this time
(which was ideal for testing).
The extenteded attribute system as implemented is very good (and in fact
I am using it for a project of mine), and provide an excellent
infrastructure for implementing ext2 and ext3 support for ACL... only
I beleive that providing an uniform interface and evaluation of ACLs that
remains independent of the filesystem is the Right Thing(tm).
Placing ACLs at the VFS level also allows subdivision of the traditional
rwx semantics. In fact, people emailed me after testing my patch have
suggested additional subdivisions of access right that would be useful
for some other non persistent filesystems (proc and devfs) such as
giving a bit for ioctl()s. And since my ACL system is based on VFS
inodes, it can be extended to sockets as well, which would make useful
connection and listen permissions, for instance.
I have not touched implementation of ACL for ext2 and ext3 yet /exactly/
because the bestbits extended attributes existed, and I felt the people
working on that code would be in an excellent position to interface with
my ACL support seamlessly.
Both codebases can be viewed as orthogonal, not competing. That's the
way I chose to look at it, and I hope others can feel the same as well.
Happy coding. :-)
-- Marc A. Pelletier
--
__________________________________________________________________
Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/
Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/
next reply other threads:[~2002-03-07 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-07 20:58 pelletierma [this message]
2002-03-07 23:25 ` Andreas Dilger
-- strict thread matches above, loose matches on Subject: below --
2002-03-05 20:32 pelletierma
2002-03-06 3:38 ` Andreas Dilger
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=3EA14851.578E6D9E.5016AB90@netscape.net \
--to=pelletierma@netscape.net \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®