Path: utzoo!utgpu!watserv1!watdragon!himacdonald
From: himacdonald@watdragon.waterloo.edu (Hamish Macdonald)
Newsgroups: comp.sys.amiga.tech
Subject: Re: resource tracking
Message-ID: <21205@watdragon.waterloo.edu>
Date: 23 Feb 90 13:28:43 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
Sender: daemon@watdragon.waterloo.edu
Distribution: na
Organization: University of Waterloo, Waterloo, Ontario
Lines: 25
In-reply-to: new@udel.edu's message of 22 Feb 90 23:55:15 GMT

>>>>> On 22 Feb 90 23:55:15 GMT, new@udel.edu (Darren New) said:

Darren> In article <21183@watdragon.waterloo.edu>
Darren> himacdonald@watdragon.waterloo.edu (Hamish Macdonald) writes:
>Question: Does I/O to Exec devices HAVE to involve message passing?
>Nowhere do
>I see a 'serial.device' task (or anything remotely interpretable as
>such) running.  

Darren> Well, when I use XOper to look at the ports list, I see a serial.device
Darren> message port generating a software interrupt into a serial.device task.
Darren> It seems to me that if you can do asynchronous calls (like post a read
Darren> and then write or wait for a timeout or ...) then you must be using 
Darren> messages. -- Darren

Fair enough.  I wanted to try XOper as well, but couldn't find it
anywhere on my friend's hard disk.   Odd that 'who' didn't pick up
that task.  Perhaps it only lists processes.

Hamish.
--
--------------------------------------------------------------------
watmath!watdragon!himacdonald     himacdonald@watdragon.waterloo.edu
"Guns seldom solve any problems; they merely decide whose will shall
prevail for the time being."      - Brian Jarvis