From owner-freebsd-hackers  Thu May 15 09:53:04 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id JAA29225
          for hackers-outgoing; Thu, 15 May 1997 09:53:04 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA29214
          for <hackers@FreeBSD.ORG>; Thu, 15 May 1997 09:53:00 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA14975; Thu, 15 May 1997 09:46:32 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199705151646.JAA14975@phaeton.artisoft.com>
Subject: Re: RFC.. Proposal.. file flag No-delete
To: julian@whistle.com (Julian Elischer)
Date: Thu, 15 May 1997 09:46:31 -0700 (MST)
Cc: terry@lambert.org, hackers@FreeBSD.ORG
In-Reply-To: <337A61BA.69D8BD19@whistle.com> from "Julian Elischer" at May 14, 97 06:07:06 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > 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.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.