Subject: Re: PROPOSAL: File flags (LONG)
To: Dr. Lex Wennmacher <wennmach@geo.Uni-Koeln.DE>
From: Eduardo E. Horvath <eeh@one-o.com>
List: tech-security
Date: 02/02/1999 09:27:43
On Mon, 1 Feb 1999, Dr. Lex Wennmacher wrote:

> 
> I have added the -i and -m options. mtree now has the following semantics:
> sappnd and schg are treated as special flags. Normally, mtree does not affect
> them.
> 
> If -u and -i are given, mtree will set the flags exactly as in the
> specificationified. -u alone will set the specified flags with the exception
> of sappnd and schg, leaving these untouched. -u and -m will set the flags as
> specified, but will clear the schg and sappnd flags.
> 
> If given without -u, -i will set schg and sappnd (leaving all other flags
> untouched), -m will reset them.
> 
> 
> 2.2  Using mtree(8) for file flags
> ----------------------------------
> 
> If you want to set the schg/sappnd flags, you would simply run
> 
> % cd /
> % mtree -i -f /etc/mtree/NetBSD.dist
> 
> or
> 
> % mtree -i -u -f /etc/mtree/NetBSD.dist
> 
> To unset the schg/sappnd flags:
> 
> % cd /
> % mtree -m -f /etc/mtree/NetBSD.dist

What about having a separate:

	/etc/mtree/NetBSD.secure

and

	/etc/mtree/NetBSD.dist

instead of separate flags?  It would seem a bit more flexible.

=========================================================================
Eduardo Horvath				eeh@one-o.com
	"I need to find a pithy new quote." -- me