public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Problems on case-sensitive file systems
Date: Wed, 22 Oct 2014 13:55:00 -0000	[thread overview]
Message-ID: <20141022135552.GC18857@calimero.vinschen.de> (raw)
In-Reply-To: <5447B69B.9020405@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 972 bytes --]

On Oct 22 07:52, Eric Blake wrote:
> On 10/22/2014 01:01 AM, Thomas Wolff wrote:
> 
> > 
> > mv XY xy does not work if XY is a directory (no effect, no message)
> 
> Might be something I can fix (I already have cygwin-local patches to
> allow 'mv A.txt a.txt', so it is probably just incomplete if directories
> aren't working).
> 
> > 
> > If I switch Windows to case-sensitivity, there is no .EXE magic (only
> > .exe magic).
> > So e.g. PING: command not found, while PING.EXE works.
> 
> I know the .exe magic I added in coreutils tries to be case insensitive,
> but I don't know if cygwin1.dll does the same; in the case of exec'ing a
> program, that's the cygwin1.dll choosing whether to try all possible cases.

Cygwin only recognizes lowercase .exe and .dll in casesensitive mode.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-10-22 13:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22  7:01 Thomas Wolff
2014-10-22 13:52 ` Eric Blake
2014-10-22 13:55   ` Corinna Vinschen [this message]
2014-10-22 14:00 ` Corinna Vinschen
2014-10-23 12:42   ` Thomas Wolff
2014-10-23 15:36     ` Corinna Vinschen
2014-10-23 17:21       ` Thomas Wolff
2014-10-23 22:05         ` Andrey Repin
2014-10-24  9:55         ` 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=20141022135552.GC18857@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.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).