*BSD News Article 26076


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!usc!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!zib-berlin.de!netmbx.de!Germany.EU.net!EU.net!sun4nl!tuegate.tue.nl!news.win.tue.nl!wzv.win.tue.nl!gvr.win.tue.nl!guido
From: guido@gvr.win.tue.nl (Guido van Rooij)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: FreeBSD: UFS bug (and fix)
Date: 15 Jan 1994 19:07:24 GMT
Organization: Eindhoven University of Technology, The Netherlands
Lines: 32
Message-ID: <2h9etc$1qt@wzv.win.tue.nl>
References: <2h8v5f$78@tyrell.tynet.sub.org>
NNTP-Posting-Host: gvr.win.tue.nl

rodney@tyrell.tynet.sub.org (Rodney Volz) writes:

>Hello,

>IMHO, there's a bug in /usr/src/sys/ufs/ufs_vnops.c concerning
>the gid-handling when creating files.

>In FreeBSD/ufs, files are always created with their group-id
>set to the group-id of their parent-directory. This behaviour
>is neither POSIX nor BSD-conforming.

This actually *is* BSD conforming. On SunOS you can even specify 
which behaviour you want in your file system at mount time. This
option is grpid.

>Posix says, that the group-id of newly created files should be set to
>the group-id of the creator. An optional Posix feature is, that
>if the parent directory has a group S-bit set, the group-id
>of the new file should be set to the group-id of its parent
>directory.

So the correct behaviour just does not exist. Best would be to make it
a mounttime option, like SunOS has. This was also discussed some time
ago on the FreeBSD hackers mailing list. I don't know if this already
been implemented but if not, it isnt that hard. 

-Guido
-- 
Guido van Rooij                 |  Internet: guido@gvr.win.tue.nl
Bisschopsmolen 16               |  Phone:    ++31.40.461433
5612 DS Eindhoven               |  ((12+144+20)+3*sqrt(4))/7 
The Netherlands                 |    +(5*11)=9^2+0