Message-Id: <m0wL67Q-000FmvC@hn.planet.gen.nz>
Date: Sat, 26 Apr 97 23:58 NZST
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: alaric AT abwillms DOT demon DOT co DOT uk
From: Lorier <lorier AT ihug DOT co DOT nz>
Subject: Re: File system ideas
Cc: opendos-developer AT delorie DOT com
Precedence: bulk

At 08:08 PM 24/04/97 +0000, Alaric B. Williams wrote:
>On 24 Apr 97 at 13:25, Lorier wrote:
>
>> 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 :) 
>
>It's called comp.os.misc, BTW!

I should start reading news :)
Personally I like mailing lists better :)
 
>> 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" :)
> 
>Well, all these features are implementable, but putting them all in makes
>the filer rapidly bigger and slower! Therefore, I would suggest opting
>for a simple architecture, but with a well defined extension system.
>
>EG, a file header has an optional field specifying a monitor module. This
>is a DLL that is notified of all access to the file. It can refuse access,
>if it performs an authentication role. It can log access. It can do all
>sorts of fun things like that.

I like it.

I think we should have a system like linux, compile in the stuff  you need :)
optimise it for your uses....