Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!sun!pitstop!sundc!seismo!uunet!microsoft!w-colinp
From: w-colinp@microsoft.UUCP (Colin Plumb)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Duplicate Volumes
Message-ID: <830@microsoft.UUCP>
Date: 8 Mar 89 03:16:42 GMT
References: <21220@agate.BERKELEY.EDU>
Reply-To: w-colinp@microsoft.uucp (Colin Plumb)
Organization: very little
Lines: 30

c60c-1ea@web-1g.berkeley.edu (Yen Yuanchi Hsieh) wrote:
> Subject:  Duplicate volumes
> Keywords:  might this work?, duplicate volumes
> 
> In the DevInfo structure, each disk seems to have a File system lock, so:
> 
>    Is it possible to traverse through DevInfo, find the correct volume 
> (as noted by the volume creation date, and the name fields), and DupLock
> the File system lock?  I'm going to try that when I get home in a couple of
> hours, let you know if I get it working...

Let me figure out what you're doing here...
the rootnode (struct RootNode) has a BPTR (rn_Info) to an info
sunstructure (struct DosInfo), which has a BPTR (di_DevInfo)
as the head of a singly linked list of DeviceList structs.

Now, these are *not* locks.  This is basically DOS's table of installed
devices; the things that are valid as device names.  A device can be on
this list with *no* outstanding locks.

Now, some of the DeviceList structs (those of type DLT_VOLUME, 2) have
a dl_LockList field, which is again a singly linked BPTR list, this
time of outstanding locks on a volume.  But this is only used when the
volume is off-line.

So I'm bot too sure what you're trying to do.
-- 
	-Colin (uunet!microsoft!w-colinp)

"Don't listen to me.  I never do." - The Doctor