Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!sdd.hp.com!spool2.mu.edu!uunet!mcsun!hp4nl!tuegate.tue.nl!svin02!eba!wjw From: wjw@eba.eb.ele.tue.nl (Willem Jan Withagen) Newsgroups: comp.sys.apollo Subject: Re: How about using ACLs? versus Unix rights? Keywords: ACL, Unix rights, not compatible? Message-ID: <1040@eba.eb.ele.tue.nl> Date: 10 Jan 91 16:16:59 GMT References: <1030@eba.eb.ele.tue.nl> <324@camdev.comm.mot.com?> Sender: news@eb.ele.tue.nl (The News system) Organization: Eindhoven University of Technology, The Netherlands Lines: 28 In article <324@camdev.comm.mot.com?> mmuegel@camdev.comm.mot.com (Mike "Happy" Muegel) writes: >In article <1030@eba.eb.ele.tue.nl> wjw@eba.eb.ele.tue.nl (Willem Jan Withagen) writes: >>I've got this directory /usr/local/include which has some extra ACL's >>appended. Now it funnctions as I expect it would, so there's nno problem >>there. >>However the Unix righs do not really make sense. Why do they have rwx for >>the world whilest they do not have it? (:-)) As most other have told me, is this a case of RTFM. :{ In the guide about making the transition to SR10 is some attention devoted to this subject. There is also extra material in the release notes in //AA/install/doc/apollo..... But what it simply boils down to is that the access rights are ordered with the most specific rights first. (Extended ACLs are very specific) And the user gets the rights with go with the first match. If that is an extended ACL then the extended mask is aplied. The resulting rights are then used as YOUR rights. So in my case wjw.staff.none is more specific, so %.local.% is ignored. and I get the rights going with wjw.staff.none ored with the extended mask. Sorry, Willem Jan Withagen. Eindhoven University of Technology DomainName: wjw@eb.ele.tue.nl Digital Systems Group, Room EH 10.10 BITNET: ELEBWJ@HEITUE5.BITNET P.O. 513 Tel: +31-40-473401 5600 MB Eindhoven The Netherlands