Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!caen!umich!terminator!pisa.ifs.umich.edu!rees
From: rees@pisa.ifs.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: APR's in general (long)
Message-ID: <4f80225e.1bc5b@pisa.ifs.umich.edu>
Date: 29 Jan 91 20:15:48 GMT
References: <9101281715.AA16081@hwcae.cfsat.honeywell.com> <1991Jan28.190504.28488@alchemy.chem.utoronto.ca>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 15

In article <1991Jan28.190504.28488@alchemy.chem.utoronto.ca>, system@alchemy.chem.utoronto.ca (System Admin (Mike Peterson)) writes:

  I agree completely - "use Aegis" should never be offered by Apollo
  as a response, and certainly should not be accepted by a user.

Hey, wait a minute -- this problem resulted precisely because the user DID
use Aegis, and set a non-bsd acl on a directory.  Now he's complaining
because he can't deal with that directory without using Aegis tools.

If you stick with bsd acls, you won't have this problem.  I think the bsd
tools that deal with acls (lsacl, chacl, and friends) were meant to give the
bsd user a minimum ability to deal with the acls he is likely to encounter
while using his node.  That's what I use them for, and they work fine for
that purpose.  It doesn't surprise me that when you start setting your own
Aegis (non-bsd) acls, those tools aren't sufficient any more.