From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Fri, 24 Oct 1997 00:00:29 -0400
From: Scott Schwartz schwartz+9fans@finch.cse.psu.edu
Subject: [9fans] group organization
Topicbox-Message-UUID: 6a9d3a92-eac8-11e9-9e20-41e7f4b1d025
Message-ID: <19971024040029.WdSG7bICMClvqwcEhAf9jeFfo42CqRWDYMJ7IOQrHqY@z>

"G. David Butler" <gdb@dbSystems.com> writes:
| Unless you have a large user population with multiple domains of
| administration

Welcome to *.edu.

| the group concept is simpler and sufficient.

It's simpler to code, but not simpler to use.

My experience is that in small organizations, everything is world
readable, owner writable, and there's one big group that everyone
(except for e.g. uucp) is in so you can have almost-world-writable
directories.  ACLs are much nicer.

| (A group is just a ACL "macro".)

I disagree.  Under that regime, in order to give a person new access to
a file, you have to create a new group, dragging the authentication
server into the picture every time you want to adjust some file.
Worse, if you really use that scheme, you can end up with an
unsightly number of such groups.