From owner-freebsd-current Tue May 27 22:02:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA24143 for current-outgoing; Tue, 27 May 1997 22:02:12 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA24138 for ; Tue, 27 May 1997 22:02:10 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.5/8.8.5) id BAA09688; Wed, 28 May 1997 01:01:59 -0400 (EDT) Date: Wed, 28 May 1997 01:01:59 -0400 (EDT) From: Charles Henrich Message-Id: <199705280501.BAA09688@crh.cl.msu.edu> To: julian@whistle.com, freebsd-current@freebsd.org Subject: Re: NEW FEATURE. BSD file NOUNLINK flag. RFC.. will commit unless.... Newsgroups: lists.freebsd.current References: <5mg1m7$chr$1@msunews.cl.msu.edu> X-Newsreader: NN version 6.5.0 CURRENT #1 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In lists.freebsd.current you write: >we have several users. all untrusted. some must be in a group 'admin' that >allows them to write to and delete anything in a certain subtree.. EXCEPT a >skeleton hierarchy of directories. [snip details] >To your comment.. This is no more 'annoying' than the 'IMMUTIBLE' flag that >presently does even more.. >personally I think it complements the other flags quite well. >comments? I think this is a wonderful idea, I could have used this myself in a similar project we've been deploying for awhile now.. -Crh -- Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich