Date: Mon, 15 Aug 2011 19:34:33 -0700 From: Yuri <yuri@rawbw.com> To: perryh@pluto.rain.com Cc: kudzu@tenebras.com, freebsd-questions@freebsd.org Subject: Re: Group permissions are broken? Message-ID: <4E49D739.9080004@rawbw.com> In-Reply-To: <4e4a2b2c.yX3blW9IEVGiJ%2BOa%perryh@pluto.rain.com> References: <4E497C2A.4060403@rawbw.com> <CAHu1Y73pODE%2BhQSWWQsjWCyjV9iq80sYqMOUKoeCMy8FSj3DFw@mail.gmail.com> <4e4a2b2c.yX3blW9IEVGiJ%2BOa%perryh@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/16/2011 01:32, perryh@pluto.rain.com wrote: > On my 8.1 system, sticky(8) says: > > A directory whose `sticky bit' is set becomes ... a directory in > which the_deletion_ of files is restricted. A file in a sticky > directory may only be_removed_ or_renamed_ if ... > > [emphasis added] > > Nothing there about the sticky bit changing the permissions required > to_overwrite_ a file, which is the subject of the current inquiry. > > Even if the sticky bit_did_ have some effect on overwriting a file, > how would that explain the_different_ behavior of the two cases shown? Actually, sticky has nothing to do with this. I originally spotted the problem on one device under /dev/ and later just made an example under tmp. Same behavior was for any other directory. I still can't get why this happened. Yuri
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E49D739.9080004>