Xref: utzoo comp.sys.amiga:14874 comp.sys.misc:1221
Path: utzoo!utgpu!jarvis.csri.toronto.edu!utcsri!me!radio!cks
From: cks@radio.toronto.edu (Chris Siebenmann)
Newsgroups: comp.sys.amiga,comp.sys.misc
Subject: Re: Cleaner PopCLI path(?)
Message-ID: <1028@radio.toronto.edu>
Date: 24 Feb 88 07:09:28 GMT
Article-I.D.: radio.1028
Posted: Wed Feb 24 02:09:28 1988
References: <10373@ut-sally.UUCP> <1943@cadovax.UUCP>
Reply-To: cks@radio.UUCP (Chris Siebenmann)
Organization: Newsaholics Anonymous
Lines: 18

In article <1943@cadovax.UUCP> keithd@cadovax.UUCP (Keith Doyle) writes:
...
>We wondered where it was getting the DF0: from, and found that it is
>hard coded in the CD program.  It is also hard coded in the Assign program
>and probably a few others.

 DF0: is what CD and ASSIGN have hard-coded as the name for directory
lock 0, which is the root device you booted from. I suspect that
Execute() is running things in a process environment with the current
directory set to a 'default' value of zero. I can't imaging why it
would do that; I suppose it's Yet Another Reason to use SyncRun from
arp.library.

-- 
	"I shall clasp my hands together and bow to the corners of the world."
			Number Ten Ox, "Bridge of Birds"
Chris Siebenmann		{allegra,mnetor,decvax,pyramid}!utgpu!radio!cks
cks@radio.toronto.edu	     or	...!utgpu!{chp!hak!ziebmef,ontmoh}!cks