Comments: Authenticated sender is <alaric+abwillms AT sdps DOT demon DOT co DOT uk>
From: "Alaric B. Williams" <alaric AT abwillms DOT demon DOT co DOT uk>
To: Lorier <lorier AT ihug DOT co DOT nz>
Date: Thu, 24 Apr 1997 20:08:19 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: File system ideas
Reply-to: alaric AT abwillms DOT demon DOT co DOT uk
CC: opendos-developer AT delorie DOT com
In-reply-to: <m0wKDIB-000FmMC@hn.planet.gen.nz>
Message-ID: <861911963.0525177.0@abwillms.demon.co.uk>
Precedence: bulk

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!
 
> 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.

It's flexible, and it's optional.

How about it?


ABW
--
Alaric B. Williams (alaric AT abwillms DOT demon DOT co DOT uk)

   ---<## OpenDOS FAQ ##>---

Plain HTML: http://www.delorie.com/opendos/faq/
            http://www.deltasoft.com/faq.html

Fancy HTML: http://www.deltasoft.com/faq0000.html