Xref: utzoo comp.bugs.sys5:1048 comp.unix.questions:15090 Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!att!cbnews!r4 From: r4@cbnews.ATT.COM (richard.r.grady..jr) Newsgroups: comp.bugs.sys5,comp.unix.questions Subject: Re: Is this a ksh bug? Message-ID: <8504@cbnews.ATT.COM> Date: 21 Jul 89 19:07:00 GMT References: <554@tijc02.UUCP> Reply-To: r4@cbnews.ATT.COM (richard.r.grady..jr) Organization: AT&T Bell Laboratories Lines: 46 In article <554@tijc02.UUCP> djm408@tijc02.UUCP (David Marks ) writes: * Has anybody seen the following behavior in ksh? * * Assuming that the current directory is /usr/me (this does not affect the bug) * * 1. make a subdirectory of the current directory that contains a colon in it: * "mkdir c:" * * 2. cd to that directory: "cd c:" Current directory is now /usr/me/c: * * 3. make a subdirectory of the current directory: "mkdir xyz" * * 4. cd to that directory: "cd xyz" * * you should get: "ksh: xyz not found" * * However, if you type cd ../c:/xyz you will have your current directory set to * /usr/me/c:/xyz with no complaints. (".." appears to mean TWO directories up * in this case!) * * Now with your current directory set to /usr/me/c:/xyz type "cd ..". * Your new current directory is /usr/me! It moved you up TWO directories! * * This was done on a VAX8600 running AT&T SYSTEMV Release 2.2 with the * 11/16/88 ksh. ksh was the login shell and CDPATH was null. * * Is this a bug? Or am I missing something in the way ksh deals with CDPATH? * * This doesn't happen on our older ksh which was the version of 2/21/85. I tried this on two systems: 1. Ksh: 11/16/88 Unix: SV Rel 3.1.1 Hardware: 3B2 This had the problem. The "cd" command behaved as in the above message. 2. Ksh: 06/03/86a Unix: SV Rel 2.0.3a Hardware: VAX This did not show the problem. The "cd" command worked normally. ------------------------------------------------------------------- Dick Grady r4@mvuxd.att.com ...!att!mvuxd!r4