From: Lee Rothstein <lee@veritech.com>
To: cygwin@cygwin.com
Subject: Re: directories named '...' (dotdotdot) do not work
Date: Wed, 02 Feb 2011 21:14:00 -0000 [thread overview]
Message-ID: <4D49C8FF.5050302@veritech.com> (raw)
In-Reply-To: <AANLkTimZ-N+2J9FgNaaB4UgvpdPArPBrb-Njfj+OR4ir@mail.gmail.com>
On 2/2/2011 3:51 PM, marco atzeri wrote:
> On Wed, Feb 2, 2011 at 9:45 PM, Corinna Vinschen wrote:
>> On Feb 1 19:37, Ralf Wildenhues wrote:
>>> The following fails for me (and web and list search haven't been
helpful):
>>> $ mkdir ...
>>> $ cd ...
>>> $ cp /usr/bin/ls.exe .
>>> $ ./ls.exe
>>> bash: ./ls.exe: No such file or directory
>>> Same with code compiled in this directory.
>>> Is this a bug or by design?
>> 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.
>> Corinna
> not working also here:
> $ uname -a
> CYGWIN_NT-5.1 1.7.8s(0.235/5/3) 20110130 23:04:08 i686 Cygwin
> $ ./ls.exe
> bash: ./ls.exe: No such file or directory
> $ ./ls
> bash: ./ls: No such file or directory
> $ ls -l
> total 128
> -rwxr-xr-x+ 1 Marco Administrators 129550 Feb 2 20:55 ls.exe
Works for me on NTFS.
$ uname -a
CYGWIN_NT-6.0-WOW64 GW2 1.7.7(0.230/5/3) 2010-08-31 09:58 i686 Cygwin
Conceivably, this could be a bug that might be important, but I
have to ask:
How good an idea is it to name a directory '...'?
Let me take a crack at an answer:
About as good an idea as embedding spaces in PATH names!
I.e, don't do it unless Mr. Bill holds a gun to your head!
Lee
--
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
next prev parent reply other threads:[~2011-02-02 21:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 19:15 Ralf Wildenhues
2011-02-02 20:46 ` Corinna Vinschen
2011-02-02 20:51 ` marco atzeri
2011-02-02 21:14 ` Lee Rothstein [this message]
2011-02-02 21:18 ` Andrew DeFaria
2011-02-02 20:56 ` Eric Blake
2011-02-02 21:29 ` Corinna Vinschen
2011-02-02 21:32 ` Corinna Vinschen
2011-02-02 21:55 ` Christian Franke
2011-02-02 22:07 ` Corinna Vinschen
2011-02-02 21:54 ` Corinna Vinschen
2011-02-02 22:01 ` Eric Blake
2011-02-02 22:12 ` Corinna Vinschen
2011-02-02 22:20 ` Corinna Vinschen
2011-02-03 6:39 ` Ralf Wildenhues
2011-02-03 9:43 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D49C8FF.5050302@veritech.com \
--to=lee@veritech.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).