Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!uunet!munnari.oz.au!kaukau.comp.vuw.ac.nz!virtue!hamish
From: hamish@waikato.ac.nz
Newsgroups: comp.sys.amiga.tech
Subject: Re: Amiga Resource tracking & Protection.
Message-ID: <208.25f3c82b@waikato.ac.nz>
Date: 6 Mar 90 02:54:00 GMT
Lines: 26

dca@toyland.UUCP writes that he would like code segment protection on
amigados, so that errant processes wouldn't stamp on his process.

I say Hear Hear!

Great idea, just what I said a while ago & got told that it was impossible,
because of the way that people abuse the MEMF_PUBLIC flag, and the fact that
libraries are shared.

So what if the libraries are shared, they don't have to be writable, or even
able to be seen by the process currently running. If the library stubs
pass a message to the actual routines in the library, & the process sleeps
until the routine is finished, (al la Unix Kernel etc).

Or is this wrong?? It seems like a solution to me. Then each process just has
to have a local jump table (or library header) to use & abuse and the system 
executes all library code. No more code trashing my errent processes, means
a more stable system.


Have I made sense to anybody sofar??

Hamish Marson.
New Zealand.

Disclaimer. All opions are my own & subject to argument!