| > From: "Mark D. Roth" <[EMAIL PROTECTED]> | > Date: Tue, 23 Jul 2002 22:02:53 -0500 | > | > On Tue Jul 23 13:31 2002 -0700, Paul Eggert wrote: | > > I'd rather try $PWD, then pwd, and fall back on /bin/pwd only if the | > > other two methods don't work. That way, the names will be nicer. | > | > That won't solve the problem, specifically because $PWD and pwd give | > the "nice" path names. The problem is that ksh is trying to interpret | > relative paths based on the string in $PWD rather than by actually | > traversing the ".." links | | OK, now I understand the problem. I also see that the problem occurs | even in absolute path names. For example, with /bin/ksh on Solaris 8: | | 33-sic $ ls -ld /tmp/usr/local/src/dummy-0.1/../../common | drwxrwxr-x 3 eggert eggert 183 Jul 24 01:54 |/tmp/usr/local/src/dummy-0.1/../../common | 34-sic $ cd /tmp/usr/local/src/dummy-0.1/../../common | /bin/ksh: /tmp/usr/local/src/dummy-0.1/../../common: not found | | What a botch!
It would be nice to document this one too...
