Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!lavaca.uh.edu!uhnix1!sugar!peter
From: peter@sugar.hackercorp.com (Peter da Silva)
Newsgroups: comp.sys.amiga.tech
Subject: Re: resource tracking
Summary: Back to the point again (and again...)
Keywords: shared memory, resource tracking.
Message-ID: <5191@sugar.hackercorp.com>
Date: 22 Feb 90 02:09:34 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> <22955@usc.edu> <5185@sugar.hackercorp.com> <22973@usc.edu>
Reply-To: peter@sugar.hackercorp.com (Peter da Silva)
Organization: Sugar Land Unix - Houston
Lines: 13

Look, the point isn't what a system call is or is not. The point is that apart
from the single special case of writing to the screen, every I/O (including
reading from the mouse or keyboard) involves messages. And the screen output
stuff also involves massive amounts of shared data.

Which UNIX doesn't bother the program with. It's a fundamental difference in
O/S philosophy. And it makes resource tracking on the Amiga a much more complex
problem. OK?
-- 
 _--_|\  Peter da Silva <peter@sugar.hackercorp.com>.
/      \
\_.--._/ I haven't lost my mind, it's backed up on tape somewhere!
      v  "Have you hugged your wolf today?" `-_-'