Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!oliveb!amiga!neil
From: neil@amiga.UUCP (Neil Katin)
Newsgroups: comp.sys.amiga
Subject: Re: The zero lock
Message-ID: <2069@amiga.UUCP>
Date: 5 May 88 02:46:35 GMT
References: <8805032135.AA26451@decwrl.dec.com>
Reply-To: neil@spam.UUCP (Neil Katin)
Organization: Commodore-Amiga Inc., 16795 Lark Ave. Suite 106, Los Gatos CA 95030
Lines: 18

In article <8805032135.AA26451@decwrl.dec.com> rmeyers@tle.dec.com (Randy Meyers 381-2743 ZKO2-3/N30) writes:
>A couple of weeks ago there was a discussion in .tech on the special
>lock 0.  Several people were badly confused as to what a lock with a
>value of zero means, and what operations are valid using this lock.
>
>AmigaDOS supports a special lock who's value is zero.  The CLI
>created when the Amiga is booted and Workbench processes all start
>out with a current directory lock of zero.  This special lock is a
>lock not on any particular file or volume: it is a lock on the device
>DF0:.

A good article, with one point that's wrong (or at least not strictly true).
A lock of zero refers to the disk handler pointed to by your process's
pr_FileSystemTask.  This is (by default) the boot disk, but can be
changed.

It is DF0: on most amiga's because most amigas were booted from df0:

	Neil Katin