Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!orchid!gamiddleton
From: gamiddleton@orchid.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: .. not considered as a botch
Message-ID: <9596@orchid.UUCP>
Date: Sun, 5-Jul-87 17:24:55 EDT
Article-I.D.: orchid.9596
Posted: Sun Jul  5 17:24:55 1987
Date-Received: Sun, 5-Jul-87 23:04:42 EDT
References: <8075@brl-adm.ARPA> <6037@brl-smoke.ARPA> <13640@mordor.s1.gov> <6054@brl-smoke.ARPA>
Reply-To: gamiddleton@orchid.waterloo.edu (Guy Middleton)
Organization: University of Waterloo
Lines: 30

In article <6054@brl-smoke.ARPA> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) ) writes:
> In article <13640@mordor.s1.gov> jdb@mordor.UUCP (John Bruner) writes:
> >I am disturbed by discussions of changes to the shell ("tcsh" and
> >"ksh", for example) which apparently cause the shell to interpret ".."
> >in a different way than the kernel does.  ....  inconsistent
> >interpretations of pathnames between programs on the same machine only
> >creates unnecessary confusion.
> 
> ... Now, after getting into the wrong
> place one too many times by "cd ..", I got sufficiently motivated to
> make this behave in an UNCONFUSING, expected way.  I don't even have
> a run-time option in my shell to get the old "cd .." behavior, and I
> have never missed it (except occasionally in a positive sense when I
> reflect on how well the new scheme works by comparison).

We have a modified shell here, which finds the real pathname of the current
directory, to avoid confusion.  It matters where you are, not how you got
there:

	Orc % ls -l /sys
	lrwxr-xr-x  1 root                11 Apr 24 19:52 /sys -> usr/src/sys
	Orc % pushd /sys
	/usr/src/sys ~ 
	Orc % pwd
	/usr/src/sys
	Orc % pushd ..
	/usr/src /usr/src/sys ~ 

__
 -Guy Middleton, University of Waterloo MFCF/ICR, gamiddleton@watmath