From owner-freebsd-hackers Thu Oct 28 5:51:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id C9B3115125 for ; Thu, 28 Oct 1999 05:51:44 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-2.enteract.com (dscheidt@shell-2.enteract.com [207.229.143.41]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id HAA19055; Thu, 28 Oct 1999 07:51:18 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Thu, 28 Oct 1999 07:51:18 -0500 (CDT) From: David Scheidt To: sthaug@nethelp.no Cc: gram@cequrux.com, hackers@freebsd.org Subject: Re: Weird /tmp behaviour In-Reply-To: <53285.941107538@verdi.nethelp.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Oct 1999 sthaug@nethelp.no wrote: > > > That's what BSD just does - see open(2): > > > > > > When a new file is created it is given the group of the directory which > > > contains it. > > > > That's pretty weird (but quite correct). Just checked on NetBSD and found > > the same. I would have expected this behaviour only if the SGID bit was set, > > not by default. > > It's always been the BSD behavior. Solaris and and some other SVR4 > systems do the sgid thing in order to make the BSD behavior possible. There is US government regulation requiring this behavior in certain government systems. The Missed 'em V behavior was created for this. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message