From owner-freebsd-hackers  Thu May 15 11:04:48 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id LAA04329
          for hackers-outgoing; Thu, 15 May 1997 11:04:48 -0700 (PDT)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA04322
          for <hackers@FreeBSD.ORG>; Thu, 15 May 1997 11:04:43 -0700 (PDT)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id KAA20864;
	Thu, 15 May 1997 10:55:48 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22)
 via SMTP by alpo.whistle.com, id smtpd020853; Thu May 15 17:55:37 1997
Message-ID: <337B4E06.1B37ADEA@whistle.com>
Date: Thu, 15 May 1997 10:55:19 -0700
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: Terry Lambert <terry@lambert.org>
CC: hackers@FreeBSD.ORG
Subject: Re: RFC.. Proposal.. file flag No-delete
References: <199705151646.JAA14975@phaeton.artisoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Terry Lambert wrote:
> 
> > > Why won't this work:
> > >
> > > chown root.x a a/b
> > > chmod 1770 a a/b
>           3770
> > > chown user.x a/d[n]
> > > chmod 1750 a/d[n]
>           3750
> > >
> >
> > because if userA (in group x) writes a file in B,
> > userB (also in group x) cannot remove it.
> > we thought of this..
> 
> How about this instead, then?
> 
> I think giving SGID the same mening relative to group for directories
> as the sticky bit is a much less intrusive change than the "delete"
> change.
> 
Isn't there a normal use for SUID and SGID fro directories?
I've been racking my brains and can't think of one,
except that SOME systems use SGID on a dir to mean "Do not inherrit
group from this directory"


julian