Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!ima!mirror!xanth!john
From: john@xanth.UUCP
Newsgroups: comp.unix.questions
Subject: Re: Access -- a program to give permissions across logins
Message-ID: <862@xanth.UUCP>
Date: Mon, 20-Apr-87 22:14:18 EST
Article-I.D.: xanth.862
Posted: Mon Apr 20 22:14:18 1987
Date-Received: Wed, 22-Apr-87 01:13:39 EST
References: <6973@brl-adm.ARPA>
Organization: Old Dominion University, Norfolk Va.
Lines: 26

In article <6973@brl-adm.ARPA>, liam%cs.qmc.ac.uk@BRL.ARPA (William Roberts) writes:
> Files inherit the group ownership of the directory in which
> they are made (I believe - references in the manual anyone?),
> so measure (1) causes student files to belong to group "seniors"
> by default. The second measure is definitely a 4.2ism: when a
> file is created, the file permissions are ANDed with NOT(umask),

Strange - I heard exactly this before from someone else (and corrected
it then, but I can't remember if it was by mail or news).

The *first*, that files inherit the group from the parent directory,
is a Berkeleyism.  Under v7, System III, System V (at least older
ones), and any other UNIXes I know of, the group of the file is the
effective gid of the creator.  Does anyone know of any other systems
that do the Berkeley thing?  v8? v9? sVr3?

The second measure, umask, has existed since v7, and is in all System
Vs, and probably all System IIIs.  It is hardly a Berkeleyism.  (If it
were, it would probably be called creatmask, and be specified in
either octal (but not negated), or symbolically, like with chmod, and
you would only be able to set it with the csh!  (major :-) ))

-- 
John Owens		Old Dominion University - Norfolk, Virginia, USA
john@ODU.EDU		old arpa: john%odu.edu@RELAY.CS.NET
+1 804 440 4529		old uucp: {seismo,harvard,sun,hoptoad}!xanth!john