Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!darwin.sura.net!haven.umd.edu!umd5.umd.edu!roissy.umd.edu!mark From: mark@roissy.umd.edu (Mark Sienkiewicz) Newsgroups: comp.os.386bsd.bugs Subject: Re: bug with ufs file creation (Not!) Date: 8 Sep 1993 17:42:25 GMT Organization: University of Maryland Lines: 27 Message-ID: <26l5i1$m5p@umd5.umd.edu> References: <CCz5n2.9v7@pilhuhn.sub.org> <GMT07Sep.93.34239@work1.rhrz.uni-bonn.de> <CD1BF5.JMM@poly.edu> NNTP-Posting-Host: roissy.umd.edu In article <CD1BF5.JMM@poly.edu> kapela@poly.edu (Theodore S. Kapela) writes: >What many vendors (including Sun) do is provide *both* policies. Sun chose >to use the SGID bit to indicate file creations under that directory are to >follow BSD semantics (which is why the SGID bit is set on new subdirs created >under that dir). (And YES, the SGID bit in most BSD systems means nothing >on a directory) Sun is required by it's Unix license to keep it's operating system compliant with the System V Interface Definition (SVID). I have NetBSD because *I* *don't* *like* *SVID*. >Since 386BSD is *BSD*, and *NOT* System V, and it is *NOT* a cross/blend >of System V and BSD, it should (and *does*) follow BSD policies. Now, if Hear! Hear! >Now, I wish people would stop assuming SunOS is the definitive Unix or BSD, >since it is *neither*. Just because XXX OS does something does not mean >it is right. SUNOS is SYSTEM V. ATT/USL/whoever started requiring that *any* system that includes *any* SYSV code *anywhere* in it must be SVID compliant. This was somewhere around V.2 or V.3.