Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!hp9000.csc.cuhk.hk!saimiri.primate.wisc.edu!sdd.hp.com!vixen.cso.uiuc.edu!howland.reston.ans.net!agate!doc.ic.ac.uk!uknet!ukc!rook.ukc.ac.uk!dac From: dac@ukc.ac.uk (D.A.Clear) Newsgroups: comp.os.386bsd.bugs Subject: Re: bug with ufs file creation Date: 07 Sep 93 14:37:43 Organization: Computing Lab, University of Kent at Canterbury, UK. Lines: 16 Message-ID: <322@rook.ukc.ac.uk> References: <CCyLF6.n6@kithrup.com> Reply-To: dac@ukc.ac.uk (David Clear) NNTP-Posting-Host: rook.ukc.ac.uk In article <CCyLF6.n6@kithrup.com> sef@kithrup.com (Sean Eric Fagan) writes: >*I* consider this a bug. It exists in every Net/2-derived system I could >play with, including BSD4.4. When creating a file, the gid given to the >file is the gid of the directory it is in, and not the gid of the process >creating the file. The following patch fixes that; it will only use the >gid of the directory if the directory's SGID bit is set. That's true BSD file creation semantics - it's probably what you want most of the time. A patch which just breaks this is probably not the best of approaches. A better solution (personally I'd leave it as it is) would be the SunOS approach whereby the semantics you favour exist - but if you mount the filesystem with the option "grpid", you get the (correct) BSD semantics. Regards, Dave.