Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: Jon_J._Brewster%Wayne-MTS@um.cc.umich.edu
Newsgroups: comp.sys.sun
Subject: Re: 4.0 likes s and S protections
Message-ID: <106501@Wayne-MTS>
Date: 30 Dec 88 17:41:35 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 14
Approved: Sun-Spots@rice.edu
Original-Date: Wed, 21 Dec 88 00:07:18 EST
X-Sun-Spots-Digest: Volume 7, Issue 82, message 2 of 18

The setgid permission on directories under 4.0 controls the group
ownership of files created within the directories.  If the setgid bit is
set, the created file inherits the group ownership of the containing
directory.  If it is not set, the file inherits the group ownership of the
creating process.  I.e., with the bit set, it works the way 3.X did...
It's documented in the man page for chmod, as well as in the release
notes.

[[ My thanks to others who have also pointed this out.  This is fully
explained in the 4.0 Change Notes, section 2.4 (I'm going to have to put a
copy next to my Sun when I do Sun-Spots from now on).  By the way, I
understand that the default semantics (those used without the set group-id
bit on) are SVID semantics.  To remove a set-gid bit with chmod, one
cannot merely "chmod 700".  One must use "chmod g-s".  --wnl ]]