Path: utzoo!attcan!uunet!crdgw1!rpi!netserv2!deven From: deven@rpi.edu (Deven T. Corzine) Newsgroups: comp.sys.amiga.tech Subject: Re: resource tracking Message-ID: Date: 22 Feb 90 19:11:10 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> <5191 Organization: Rensselaer Polytechnic Institute, Troy, NY Lines: 27 In-Reply-To: peter@sugar.hackercorp.com's message of 22 Feb 90 02:09:34 GMT On 22 Feb 90 02:09:34 GMT, peter@sugar.hackercorp.com (Peter da Silva) said: Peter> Look, the point isn't what a system call is or is not. The Peter> point is that apart from the single special case of writing to Peter> the screen, every I/O (including reading from the mouse or Peter> keyboard) involves messages. And the screen output stuff also Peter> involves massive amounts of shared data. Consider. A system call does not HAVE to be I/O. Yes, all I/O to Exec devices and AmigaDOS filesystems involves message passing. Not all _system_ calls do. Does AddTask() use messages? No. Don't try telling me it's not a system call. Peter> Which UNIX doesn't bother the program with. It's a fundamental Peter> difference in O/S philosophy. And it makes resource tracking on Peter> the Amiga a much more complex problem. OK? More complex, yet if you intercept at the message-passing level, you're in the clear... (largely) Deven -- Deven T. Corzine Internet: deven@rpi.edu, shadow@pawl.rpi.edu Snail: 2151 12th St. Apt. 4, Troy, NY 12180 Phone: (518) 274-0327 Bitnet: deven@rpitsmts, userfxb6@rpitsmts UUCP: uunet!rpi!deven Simple things should be simple and complex things should be possible.