Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: brent%terra@sun.com (Brent Callaghan)
Newsgroups: comp.sys.sun
Subject: Re: determining the real directory when using automounts
Message-ID: <89811@sun.uucp>
Date: 28 Feb 89 11:26:43 GMT
References: <8902090049.AA21344@hector.homer.nj.att.com>
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 22
Approved: Sun-Spots@rice.edu
Original-Date: 15 Feb 89 06:39:41 GMT
X-Sun-Spots-Digest: Volume 7, Issue 172, message 2 of 15

In article <8902090049.AA21344@hector.homer.nj.att.com>, ekrell@ulysses.att.com writes:
> In ksh, pwd is a builtin which returns the "logical" name of the current
> working directory, so if you "cd /foo/bar", pwd always returns "/foo/bar",
> even if you're in a different place as a consequence of following symbolic
> links or other such wierdness.

Just to follow up on Eduardo's comment: I automount my home directory.
I'm a ksh user so I see what I expect to see when I do a pwd in my home
directory "/home/sparky/brent".  The C shell also maintains $PWD.  You can
get the same effect as the ksh builtin just by setting up pwd as an alias
to echo $PWD.  Just make sure that the csh hardpaths option isn't set (I
don't think it is by default).

The mount point names are a little more attractive if you use the 4.0.1
automounter.  The "/tmp_mnt/autoa12345" mount points have been replaced by
a scheme that gives you the same path except for a prepended "/tmp_mnt"
e.g. a /bin/pwd of my home directory now gives
"/tmp_mnt/home/sparky/brent".

Made in New Zealand -->  Brent Callaghan  @ Sun Microsystems
			 uucp: sun!bcallaghan
			 phone: (415) 336 1051