From owner-freebsd-hackers  Wed May 14 15:55:31 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id PAA11336
          for hackers-outgoing; Wed, 14 May 1997 15:55:31 -0700 (PDT)
Received: from kithrup.com (kithrup.com [205.179.156.40])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA11330
          for <hackers@freebsd.org>; Wed, 14 May 1997 15:55:29 -0700 (PDT)
Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id PAA12200; Wed, 14 May 1997 15:55:24 -0700
Date: Wed, 14 May 1997 15:55:24 -0700
From: Sean Eric Fagan <sef@Kithrup.COM>
Message-Id: <199705142255.PAA12200@kithrup.com>
To: julian@whistle.com
Subject: Re: RFC.. Proposal.. file flag No-delete
Newsgroups: kithrup.freebsd.hackers
In-Reply-To: <337A35E7.5656AEC7.kithrup.freebsd.hackers@whistle.com>
Organization: Kithrup Enterprises, Ltd.
Cc: hackers@freebsd.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In article <337A35E7.5656AEC7.kithrup.freebsd.hackers@whistle.com> you write:
>basically I need to be able to set up a skeleton that cannot be
>alterd or removed, but can be added to by non root users.

I don't particularly like it, but, then, I'd rather see ACL's added than
more specialized bits used.

However, I have to ask... would a union filesystem (with a read-only FS as
the skeleton/base) do what you want?

Sean.