Re: directories named '...' (dotdotdot) do not work

[Corinna Vinschen <corinna-cygwin at cygwin dot com>]

On Feb  2 22:55, Christian Franke wrote:
> Corinna Vinschen wrote:
> >
> >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.
> >
> 
> At least on XP cmd and others could not be run from a subdir below "...":
> 
> $ /bin/pwd
> /tmp/...
> 
> $ cmd.exe /c cd
> C:\cygwin\tmp
> 
> $ mkdir x
> 
> $ cd x
> 
> # /bin/pwd
> /tmp/.../x
> 
> # cmd.exe /c cd
> -bash: /cygdrive/c/WINDOWS/system32/cmd.exe: Not a directory
> 
> 
> Same for "....", ".....", ....
> 
> Different path checking in win32api layer and ntdll layer ?

Yes, definitely.  I explained that in
http://cygwin.com/ml/cygwin/2011-02/msg00078.html

On the Win32 level the path is massaged so that it follows DOS filename
conventions.  This is not done on the native NT level.  The long-path
prefix when used on the Win32 level (but only in the UNICODE API) disables
the DOSifying and just passes the path through to the native NT API.

> I would suggest to either quote or reject "..." in Cygwin.

Given that the path works fine except for starting an executable, and
given that starting an app works fine in Vista and later, there's no
reason to disallow the "..." path component entirely.  I'm not giving in
to the old DOS path conventions, unless there's absolutely no way around
it.


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