Message-Id: <199704241124.NAA18256@grendel.sylaba.poznan.pl> Comments: Authenticated sender is From: "Mark Habersack" Organization: PPP (Pesticide Powered Pumpkins) To: Lorier Date: Thu, 24 Apr 1997 13:21:44 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: File system ideas Reply-to: grendel AT hoth DOT amu DOT edu DOT pl CC: physmsa AT cantua DOT canterbury DOT ac DOT nz (Mr M S Aitchison), alaric AT abwillms DOT demon DOT co DOT uk, opendos-developer AT delorie DOT com In-reply-to: Precedence: bulk Once upon a time (on 24 Apr 97 at 13:25) Lorier said: > >I've been toying with attributed file system ideas for a few years now. > >Combining a general attribute system with file system monitors (triggered > >and monitored events) you could do some fairly interesting things. I'd be > >willing to discuss ideas with you. > > Hmm, we almost need a > "operating-system-general-discussion-and-theory-that-doesnt-really-amount-to > -terribly-much-but-has-some-really-fascinating-ideas" mailing list :) > > Post your ideas, they sound fascinating. apparently the Vax have some > scheme where you can place "alarms" on certain files for when they are > accessed. (for example the shadow password file... someone reads it who > isn't in the "your allowed" catagory mails root, and runs shutdown -h now" > :) Also a quota feature would be nice - not based on UID/GID but rather on file's associated attributes. A great thing for "flexible" swapfiles, database "trashcans" etc. ================================================== Stand straight, look me in the eye and say goodbye Stand straight, we drifted past the point of reasons why. Yesterday starts tommorow, tommorow starts today And the problems seem to be we're picking up the pieces of a ricochet...