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/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Mar 07 2002 - 21:01:08 EST