Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!cbmvax!jesup
From: jesup@cbmvax.UUCP (Randell Jesup)
Newsgroups: comp.sys.amiga.tech
Subject: Re: What is my name?
Message-ID: <7371@cbmvax.UUCP>
Date: 20 Jul 89 06:12:49 GMT
References: <26385@agate.BERKELEY.EDU> <7330@ardent.UUCP> <26406@agate.BERKELEY.EDU> <7374@ardent.UUCP>
Reply-To: jesup@cbmvax.UUCP (Randell Jesup)
Organization: Commodore Technology, West Chester, PA
Lines: 18

In article <7374@ardent.UUCP> rap@peck.ardent.com (Rob Peck) writes:
>I now understand your question exactly and I agree that the current
>directory path name listing is inadequate.  Looks like you have some
>work on your hands.  To know exactly where-from the binary that is
>running was drawn, you need to know both the PATH and the command
>that was issued, so you'd have to get to the command history of
>the originating CLI (if there was one).  Frankly, without doing
>both of these, I cannot see how a binary can identify the directory
>in which it resides and from which it was called.     AAARRRGGGHHH!

	Quite true, the current CLI/Shell doesn't preserve the needed
information (some other shells do).  The ability to get to the file the
program was run from should be addressed in 1.4.

-- 
Randell Jesup, Keeper of AmigaDos, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com  BIX: rjesup  
Common phrase heard at Amiga Devcon '89: "It's in there!"