On Feb 2 22:28, Corinna Vinschen wrote: > On Feb 2 13:56, Eric Blake wrote: > > On 02/02/2011 01:45 PM, Corinna Vinschen wrote: > > > Works fine for me: > > > > > > $ uname -a > > > CYGWIN_NT-6.1 vmbert7 1.7.7(0.230/5/3) 2010-08-31 09:58 i686 Cygwin > > > $ cd tmp > > > $ mkdir ... > > > $ cd ... > > > $ cp /usr/bin/ls.exe . > > > $ ./ls > > > ls.exe > > > > > > I tried on NTFS, Samba and NFS. > > > > Difference in Windows version? > > > > $ uname -a > > CYGWIN_NT-5.1 LOUNGE 1.7.7(0.230/5/3) 2010-08-31 09:58 i686 Cygwin > > $ pwd > > /tmp/... > > $ ls > > ls.exe > > $ ./ls > > bash: ./ls: No such file or directory > > > > or maybe in bash versions (since I did just upgrade bash from 3.2 to 4.1)? > > No, I'm using tcsh. Apparently you're right, it doesn't work in > XP, but it works in W7. Looks like Microsoft reworked the CreateProcess > call at some point. I have an idea how this might be possible to > workaround. Stay tuned.
Btw., the "..." directory is not recognized at all by cmd.exe. If you try to cd into it, it's simply ignored. If you set the CWD to it and start cmd, cmd thinks it is in the parent directory. This occurs on XP *and* W7. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
