Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!VAX1.CC.UAKRON.EDU!mcs.kent.edu!usenet.ins.cwru.edu!ncoast!allbery
From: allbery@NCoast.ORG (Brandon S. Allbery KB8JRR)
Newsgroups: comp.unix.internals
Subject: Re: What does SUID, SGID and Sticky bits do on inappropriate files?
Message-ID: <1991Jan11.032444.16654@NCoast.ORG>
Date: 11 Jan 91 03:24:44 GMT
References: <1990Dec28.061246.29268@kithrup.COM> <5114@auspex.auspex.com> <5128@auspex.auspex.com>
Reply-To: allbery@ncoast.ORG (Brandon S. Allbery KB8JRR)
Followup-To: comp.unix.internals
Organization: North Coast Computer Resources (ncoast)
Lines: 22

As quoted from <5128@auspex.auspex.com> by guy@auspex.auspex.com (Guy Harris):
+---------------
| In article <5114@auspex.auspex.com> guy@auspex.auspex.com (Guy Harris) writes:
|  >>>SunOS and maybe other Unixes use g+s on a directory to produce sticky gid's:
|  >
|  >4.3BSD added this (it may have appeared in other systems before that),
| 
| Said brain saw "sticky" and "directory" and immediately read "sticky
| directory", not noting that the bit being talked about was the set-GID
+---------------

My fault, I being the one who posted the "| >>>" line:  I made the same
mistake while composing it ("g+s" with "s" meaning "sticky").  Of course, one
could call the behavior "setgid", although with rather different meaning from
the usual....

++Brandon
-- 
Me: Brandon S. Allbery			    VHF/UHF: KB8JRR on 220, 2m, 440
Internet: allbery@NCoast.ORG		    Packet: KB8JRR @ WA8BXN
America OnLine: KB8JRR			    AMPR: KB8JRR.AmPR.ORG [44.70.4.88]
uunet!usenet.ins.cwru.edu!ncoast!allbery    Delphi: ALLBERY