Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!psuvax1!rutgers!cbmvax!uunet!nuchat!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.tech Subject: Re: resource tracking Message-ID: <5201@sugar.hackercorp.com> Date: 25 Feb 90 05:33:44 GMT References: <355.25C92297@weyr.FIDONET.ORG> <926@tardis.Tymnet.COM> Organization: Sugar Land Unix - Houston Lines: 23 > 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. Argh... OK, let's put it this way. Come up with a program that does soemthing useful and doesn't do any IPC at all. About the only thing I can think off is one that runs ONLY under the CLI, has no diagnostic messages, and toggles the 7kHz filter on and off (or does some other trivial hardware hackery (or hijackery)). IPC is integral to the Amiga. Sharing memory between a bunch of tasks is not something you can get away from. It's rare on UNIX. Maybe I need a disclaimer: "If this message uses different magic incantations than the ones you're used to, try to see if that effects the content before flaming"? -- _--_|\ Peter da Silva . / \ \_.--._/ I haven't lost my mind, it's backed up on tape somewhere! v "Have you hugged your wolf today?" `-_-'