Path: utzoo!mnetor!uunet!nuchat!flatline!sugar!peter
From: peter@sugar.UUCP (Peter da Silva)
Newsgroups: comp.sys.amiga
Subject: Device List and monitoring devices.
Message-ID: <1475@sugar.UUCP>
Date: 21 Feb 88 17:35:41 GMT
Organization: Sugar Land UNIX - Houston, TX
Lines: 30
Keywords: Details, details. AmigaDOS and crystal balls.
Summary: Once again into the breach, my friends...

Well, I need some info. The AmigaDOS manual is not exactly clear as crystal.

If you have two file names and want to determine if they refer to the
same device, how do you do it? DeviceProc?

If you call DeviceProc and don't do anything with the Lock returned in
IoErr(), what happens to it? Does it leave a loose lock? Is it the ParentDir
lock, or a root lock, or what?

When you come across a DevList entry with Type equal to dt_volume, how
do you map it to a physical volume ID? Go through the DevList looking
for dt_device entries with the same Handler process?

How does Workbench guarantee that it opens the same volume when you have
two volumes of the same name? Keep a Lock on the volume? Must be more
than that because closing the last lock on a volume releases it, so
Workbench can't keep ahold of any for volumes with no open windows.

My theory: it keeps the timestamp, then when you try to open the disk
it goes through the DevList looking for a device with the same stamp
and name... then it DupLocks the Lock. If the volume's not mounted it
does a Lock on it and then checks the timestamp again... and so on.

It could also keep its set of locks and UnLock them after getting a DiskChange
message, and relock them after it's rescanned the DevList...

Or does it have a backdoor????
-- 
-- Peter da Silva  `-_-'  ...!hoptoad!academ!uhnix1!sugar!peter
-- Disclaimer: These U aren't mere opinions... these are *values*.