From: Ronald G Minnich <rminnich@lanl.gov>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] fuse bashing
Date: Wed, 25 Jan 2006 08:45:17 -0700 [thread overview]
Message-ID: <43D79D0D.8000900@lanl.gov> (raw)
In-Reply-To: <20276.1138167055@piper.nectar.cs.cmu.edu>
Dave Eckhardt wrote:
>>no ACLs (I'm convinced that the stat and wstat could be trivially
>>extended to support this --- 9p2000.acl)
>
>
> I assume ACL semantics would need to be outside the protocol, but
> have you found an ACL system you like?
I'm not so sure it has to be outside the protocol. We've already
extended stat/wstat with .u, and it was not that big a deal. The *stat
packets are a very good design, and I think could be stretched for ACLs.
> The part of AFS I like is that every user can define new groups.
> Once "owner" and "group" can be arbitrary sets of people, it's
> not clear to me that you need more than "owner, group, world".
Data General AOS/VS had a pretty usable ACL scheme. ACLs were simple
sequences of tuples: (re, permission)+ -- IIRC, it's been 24 years, and
I can't find that manual -- so, for example, you might have:
(rminnich,readwrite):(sys+, read):(myfriends, readwrite)
and so on.
In practice, everybody did user, group, world, just with re's instead of
numbers; I think I agree with you. It's too hard to think about much
else. I didn't say people NEED ACLs, they just WANT ACLs. As I used to
say to my kids all the time, "You don't need that, you want that". After
about 10 years, they got my point.
ACLs are the new fad, and they're going in, with silly bugs to boot
(ACLs have been NOT fun on linux), and I really doubt in the end we'll
go much beyond user, group, world.
ron
next prev parent reply other threads:[~2006-01-25 15:45 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 17:06 Russ Cox
2006-01-23 17:28 ` Ronald G Minnich
2006-01-23 17:44 ` David Leimbach
2006-01-23 18:07 ` Eric Van Hensbergen
2006-01-23 18:13 ` Bruce Ellis
2006-01-23 20:31 ` David Leimbach
2006-01-23 20:33 ` Ronald G Minnich
2006-01-23 23:28 ` Dan Cross
2006-01-23 23:53 ` David Leimbach
2006-01-24 0:07 ` Ronald G Minnich
2006-01-25 19:58 ` Enache Adrian
2006-01-25 20:30 ` Christoph Lohmann
2006-01-25 20:51 ` Ronald G Minnich
2006-01-25 21:09 ` Bruce Ellis
2006-01-25 20:50 ` Ronald G Minnich
2006-01-25 21:09 ` Enache Adrian
2006-01-24 0:12 ` John Barham
2006-01-25 5:29 ` Dave Eckhardt
2006-01-25 15:38 ` Ronald G Minnich
2006-01-25 21:31 ` Dave Eckhardt
2006-01-26 1:16 ` erik quanstrom
2006-01-25 5:30 ` Dave Eckhardt
2006-01-25 7:46 ` Jack Johnson
2006-01-25 8:11 ` Lyndon Nerenberg
2006-01-25 8:18 ` Lyndon Nerenberg
2006-01-25 9:46 ` Andriy G. Tereshchenko
2006-01-25 15:45 ` Ronald G Minnich [this message]
2006-01-23 17:51 ` C H Forsyth
2006-01-23 17:46 ` David Leimbach
2006-01-23 20:08 ` Ronald G Minnich
2006-01-23 18:46 ` Skip Tavakkolian
2006-01-24 2:22 ` Latchesar Ionkov
2006-01-24 8:37 ` Charles Forsyth
2006-01-24 9:41 ` Charles Forsyth
2006-01-24 10:04 ` Charles Forsyth
[not found] <000001c620ca$f86f1570$14aaa8c0@utelsystems.local>
2006-01-24 9:46 ` "Nils O. Selåsdal"
2006-01-24 20:10 quanstro
2006-01-24 21:37 ` Eric Van Hensbergen
2006-01-24 23:14 ` Charles Forsyth
2006-01-25 0:26 ` Latchesar Ionkov
2006-01-25 0:25 ` Latchesar Ionkov
2006-01-25 1:31 ` erik quanstrom
2006-01-25 1:40 ` Latchesar Ionkov
2006-01-25 1:42 ` Eric Van Hensbergen
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=43D79D0D.8000900@lanl.gov \
--to=rminnich@lanl.gov \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).