9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] book chapters
Date: Fri, 27 Jun 2003 22:10:48 -0400	[thread overview]
Message-ID: <200306280210.h5S2Am723171@augusta.math.psu.edu> (raw)
In-Reply-To: Your message of "Fri, 27 Jun 2003 21:03:38 EDT." <20030628010338.3523.qmail@g.bio.cse.psu.edu>

> | I haven't, because groups serve nicely as ACLs,
>
> I disagree.  ACLs are things that any user can set on any of their files.
> That's the opposite of predefined groups stored on the BOFH's auth
> server.

I just want to point out that the ability to write user-level file
servers allows one to easily implement ACL's at that level.  It's
not convenient for, e.g., access to a fossil or some similar large
fileserver (think of the mess an ACL-enabled overlay would be), but
it works for other things.

> Do you really want to define groups for all 50000! combinations of users
> on PSUVM?  I'd rather just attach the access list to the file itself.

There are 2^50000 - 1 such combinations (assuming one ignores the group
with no one in it); a lot more than 50000!.  Besides, I thought PSUVM was
gone?  I'm out of touch with what's happening in Happy Valley, I guess.

> | I wonder if the people who rave about ACLs are actually attached to
> | some aspect of a particular implementation,
>
> The one in Primos (and Multics, I guess) was certainly beautiful,
> but it's the actual effect that I'm attached to.

I think the major benefit of ACL systems is that most implementations
don't require administrator intervention to set up or maintain them
(some do).

	- Dan C.



  reply	other threads:[~2003-06-28  2:10 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-27  9:47 pac
2003-06-27 10:22 ` matt
2003-06-27 22:08 ` Joel Salomon
2003-06-27 22:12   ` Geoff Collyer, geoff
2003-06-27 23:39     ` boyd, rounin
2003-06-28  1:03     ` Scott Schwartz
2003-06-28  2:10       ` Dan Cross [this message]
2003-06-28  2:27         ` Dan Cross
2003-06-29 17:55     ` Jack Johnson
2003-06-30 11:17       ` matt
2003-06-30 13:43         ` ron minnich
2003-06-30 14:02           ` matt
2003-06-30 16:56           ` Jack Johnson
2003-06-30 17:16             ` boyd, rounin
2003-06-30 17:19               ` ron minnich
2003-06-30 17:24                 ` ron minnich
2003-06-30 17:29                   ` boyd, rounin
2003-06-30 18:40             ` rog
2003-06-30 23:16               ` Kenji Arisawa
2003-06-30 23:24                 ` boyd, rounin
2003-07-01  1:44                 ` David Presotto
2003-07-01 11:27                   ` Kenji Arisawa
2003-07-01 11:32                     ` David Presotto
2003-07-01  9:51             ` matt
2003-06-27 22:36   ` William Ahern
2003-06-27 22:28 Joel Salomon
2003-06-27 22:26 ` Geoff Collyer, geoff
2003-06-27 23:43 ` boyd, rounin
2003-06-27 23:46   ` Geoff Collyer, geoff
2003-06-28  0:53     ` Dennis Ritchie
2003-06-28 17:44 A. Baker
2003-06-29  4:38 ` Dennis Ritchie
2003-06-30 18:17 Richard C Bilson
2003-07-01 17:48 A. Baker
2003-07-02  0:27 ` Dennis Ritchie

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=200306280210.h5S2Am723171@augusta.math.psu.edu \
    --to=cross@math.psu.edu \
    --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).