Below is a report made via the Debian bug tracking system. I'm guessing that when handling `..', ksh is trying to use what it previously knew to be the path to the current directory whereas the other shells aren't specifying a path.
Oliver ------- Forwarded Message Date: Tue, 03 Apr 2012 16:57:12 +0200 From: Vincent Lefevre <vinc...@vinc17.net> To: Debian Bug Tracking System <sub...@bugs.debian.org> Subject: Bug#667038: ksh93 fails to detect renamed current or parent directory Package: ksh Version: 93u-1 Severity: normal ksh93 fails on the following script: ypig:~> cat tst.sh mkdir tmpdir1 cd tmpdir1 mv ../tmpdir1 ../tmpdir2 cd .. rmdir tmpdir2 ypig:~> ksh93 tst.sh tst.sh[4]: cd: ..: [No such file or directory] rmdir: failed to remove `tmpdir2': No such file or directory dash, bash, zsh, pdksh, mksh and posh all behave correctly on this example. Note: similar problem when renaming a parent directory. - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experi mental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ksh depends on: ii libc6 2.13-27 ksh recommends no packages. ksh suggests no packages. - -- no debconf information ------- End of Forwarded Message -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org