Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!clyde!cbatt!cwruecmp!hal!ncoast!tdi2!brandon
From: brandon@tdi2.UUCP (Brandon Allbery)
Newsgroups: comp.unix.questions
Subject: Re: Access -- a program to give permissions across logins
Message-ID: <345@tdi2.UUCP>
Date: Thu, 23-Apr-87 10:55:22 EDT
Article-I.D.: tdi2.345
Posted: Thu Apr 23 10:55:22 1987
Date-Received: Wed, 29-Apr-87 06:56:55 EDT
References: <6973@brl-adm.ARPA>
Reply-To: brandon@tdi2.UUCP (Brandon Allbery)
Followup-To: comp.unix.questions
Organization: Tridelta Industries, Inc., Mentor, Ohio
Lines: 22

Quoted from <6973@brl-adm.ARPA> ["Re: Access -- a program to give permissions across logins"], by liam%cs.qmc.ac.uk@BRL.ARPA (William Roberts)...
+---------------
| >set of users (e.g. students in a class) which are to be protected from
| >each other (can't read or destroy each other's homework, for example)
| >and one or more "senior" logins (e.g. the teacher of the class, TAs for
| >logins to all be accessible to the senior, administrative logins. The
|      
| The way to do this is to use UNIX group permissions. In 4.2 BSD
| Files inherit the group ownership of the directory in which
| they are made (I believe - references in the manual anyone?),
+---------------

May be true for BSD, but under System V a file is created with the gid of the
creator.  I suspect the same is true for BSD, although there may be some kind
of setgid-directory semantics to get the effect you describe.

++Brando
-- 
Brandon S. Allbery	           UUCP: cbatt!cwruecmp!ncoast!tdi2!brandon
Tridelta Industries, Inc.         CSNET: ncoast!allbery@Case
7350 Corporate Blvd.	       INTERNET: ncoast!allbery%Case.CSNET@relay.CS.NET
Mentor, Ohio 44060		  PHONE: +1 216 255 1080 (home +1 216 974 9210)