9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: G. David Butler gdb@dbSystems.com
Subject: [9fans] group organization
Date: Thu, 23 Oct 1997 22:26:13 -0500	[thread overview]
Message-ID: <19971024032613.b8oLPdhsu3ahV1u8uqTRN7uVHfrNvvlObS8VM83EkAY@z> (raw)

From: Scott Schwartz <schwartz@finch.cse.psu.edu>
>
>I hate to raise heretical notions, but I really don't think
>user/group/other works very often, and it's not worth trying to tweak
>it.  If a filesystem object isn't world readable, then 90% of the time
>I want an access control list (maybe just for directories) to specify
>who gets to do what with that file.  Allowing the authentication
>system to put users in multiple catagories, even if you can change
>them easily, doesn't seem to me to be the right solution.

I would like to see an efficient ACL implementation to consider.

Unless you have a large user population with multiple domains of
administration the group concept is simpler and sufficient.  (A
group is just a ACL "macro".)  For my part, I like the tighter
security of P9 over *NIX.  If you have followed the list you will
notice I have tightened it further.  (I have effectively excluded
"none" from "other".)

>"If I want Multics, I know where to find it."
Yes, but is it available in source and does it run on a PC? :->




             reply	other threads:[~1997-10-24  3:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-24  3:26 G.David [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-10-24  4:30 G.David
1997-10-24  4:00 Scott
1997-10-24  0:22 Scott
1997-10-23 23:45 G.David
1997-10-23 15:45 Kenji
1997-10-22 15:49 G.David
1997-10-22  7:10 Kenji

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=19971024032613.b8oLPdhsu3ahV1u8uqTRN7uVHfrNvvlObS8VM83EkAY@z \
    --to=9fans@9fans.net \
    /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).