Path: utzoo!utgpu!water!watmath!watcgl!watsol!bmacintyre
From: bmacintyre@watsol.waterloo.edu (Blair MacIntyre)
Newsgroups: comp.sys.amiga
Subject: PATH: device
Message-ID: <3903@watcgl.waterloo.edu>
Date: 6 Apr 88 17:30:33 GMT
Sender: daemon@watcgl.waterloo.edu
Reply-To: bmacintyre@watsol.waterloo.edu (Blair MacIntyre)
Distribution: world
Organization: Centre for the OED, 2nd Edition
Lines: 32

[]

Well, I'm still playing at writing a PATH: device.  Since this is my first
jump into the wonderful world of AmigaDOS devices, I have a few questions:
 - From going through the AmigaDOS Technical Ref Manual, the packets I have
   decided I should handle (for a read-only path device) are:
     ExamineObject, ExamineNext, DiskInfo, Parent, LocateObject, FreeLock
     ( perhaps Duplock or Copydir or whatever as well )
   The thing I'm wondering is what to do about Locks.

   - I assume when I am returning a new lock I allocate it, but do I link it
     into the list of Locks in the DeviceList struct ( I'm doing this from
     memory from last night - I hope I have the names correct )
   - do I have to keep track of the locks if I don't do the linking ( ie. do
     I need to worry about it or does someone else )

 - who passes these packets?

( damn, there were some other questions ... oh well - any info would be 
  great ).

I realize that other people are probably doing this, but I want to do it as
much for a learning experience as anything!  

Thanx in advance.
Blair

--
===========================================================================///=
Blair MacIntyre (bmacintyre@watsol.waterloo.edu) ( Long live the Amiga!! )///
"Violence is the last resort of the incompetent" - Issac Asimov       \\\///
=Have you hugged your dragon today??=(how about your SO??)=============\XX/====