From owner-freebsd-hackers Wed May 14 17:41:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA17693 for hackers-outgoing; Wed, 14 May 1997 17:41:18 -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 RAA17688 for ; Wed, 14 May 1997 17:41:15 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA13765; Wed, 14 May 1997 17:35:02 -0700 From: Terry Lambert Message-Id: <199705150035.RAA13765@phaeton.artisoft.com> Subject: Re: RFC.. Proposal.. file flag No-delete To: julian@whistle.com (Julian Elischer) Date: Wed, 14 May 1997 17:35:02 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: <337A35E7.5656AEC7@whistle.com> from "Julian Elischer" at May 14, 97 03:00:07 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 > a skeleton of directories and files which must not be removed except > by root, intermixed with files that should be able to be added and > removed by users of a particular group. > (M) = directory > [N] = file > > (A)----(B)----[C] > | > \-(D) > > We want non root members of group 'x' to be able to > add files or directories to directories A, B or D, and delete > them again, > however they must not be able to delete A,B,C, or D > non members of group 'x' must only be able to write into D in > the case where D is owned by them. (D represents several > directories with different owners(e.g. home directories)) > > this seems to be an easy problem, but it turns out that > it is not immediatly solvable using standard semantics. Why won't this work: chown root.x a a/b chmod 1770 a a/b chown user.x a/d[n] chmod 1750 a/d[n] ? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.