From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: case sensitivity bug?
Date: Wed, 19 Oct 2016 15:09:00 -0000 [thread overview]
Message-ID: <01783187-fd5e-12b2-a0ac-c77ca0090ebb@cornell.edu> (raw)
In-Reply-To: <20161019112735.GB4801@calimero.vinschen.de>
On 10/19/2016 7:27 AM, Corinna Vinschen wrote:
> On Sep 20 20:33, Ken Brown wrote:
>> I've set up my Cygwin installation to be case sensitive, following the instructions at
>>
>> https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive
>>
>> But it doesn't seem to be working as I expect. For example:
>>
>> $ mkdir a
>>
>> $ mkdir A
>>
>> $ ls -al [aA]
>> a:
>> total 100
>> drwxr-xr-x+ 1 kbrown None 0 2016-09-20 20:18 ./
>> drwxrwxrwt+ 1 kbrown-admin None 0 2016-09-20 20:19 ../
>>
>> A:
>> total 100
>> drwxr-xr-x+ 1 kbrown None 0 2016-09-20 20:19 ./
>> drwxrwxrwt+ 1 kbrown-admin None 0 2016-09-20 20:19 ../
>>
>> $ mv a A
>> mv: cannot move 'a' to a subdirectory of itself, 'A/a'
>>
>> Why does mv think that A and a are the same directory?
>>
>> Here's another example, where mv should simply do a rename, but it doesn't:
>>
>> $ rmdir A
>>
>> $ mv a A
>>
>> $ ls -al a
>> total 100
>> drwxr-xr-x+ 1 kbrown None 0 2016-09-20 20:18 ./
>> drwxrwxrwt+ 1 kbrown-admin None 0 2016-09-20 20:30 ../
>>
>> $ ls -al A
>> ls: cannot access 'A': No such file or directory
>>
>> cygcheck output is attached.
>
> Looks like a *very* old misbehaviour. I applied a patch to Cygwin
> to fix this. I'll create a snapshot later today, please test.
That fixes it. Thanks.
Ken
--
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
prev parent reply other threads:[~2016-10-19 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 8:50 Ken Brown
2016-09-21 10:45 ` Andrey Repin
2016-09-21 16:59 ` Brian Inglis
2016-09-21 17:45 ` Ken Brown
2016-09-22 12:32 ` Brian Inglis
2016-10-19 11:29 ` Corinna Vinschen
2016-10-19 15:09 ` Ken Brown [this message]
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=01783187-fd5e-12b2-a0ac-c77ca0090ebb@cornell.edu \
--to=kbrown@cornell.edu \
--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).