Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!udel!new
From: new@udel.edu (Darren New)
Newsgroups: comp.sys.amiga.tech
Subject: Re: resource tracking
Keywords: What is a system call???
Message-ID: <12246@nigel.udel.EDU>
Date: 26 Feb 90 17:58:48 GMT
References: <355.25C92297@weyr.FIDONET.ORG> <926@tardis.Tymnet.COM> <352@amgraf.UUCP> <5156@sugar.hackercorp.com> <5159@sugar.hackercorp.com> <9704@cbmvax.commodore.com> <5178@sugar.hackercorp.com> <315@spot.wbst128.xerox.com> <1543@zipeecs.umich.edu>
Sender: usenet@udel.EDU
Reply-To: new@udel.edu (Darren New)
Organization: University of Delaware
Lines: 18

In article <1543@zipeecs.umich.edu> gilgalad@eecs.umich.edu (Ralph Seguin) writes:
>I love the Amiga's IPC method: nonreplicating messages.  Why on earth others
>haven't seen the wisdom in this is beyond me.  Actually, people are starting
>to catch on.

I've been trying to think of a clean way to allow a multi-user version of this
kind of thing.  Somethink like having each field of a message being tagged
with flags saying whether it was to be interpreted as an address and if
so, whether it may be read and/or written by the receiver. If you have
come up with (or seen) a clean solution, please let me know. Maybe
segments a la Multics?

>What's a KERNAL anyways?  (don't mind me, I'm just being a smart ass).
  I always thought it was the part you couldn't replace without
  being privledged.   Hence, on a single user micro, there IS no 
  kernal (kernel?) just libraries.

           -- Darren