This is the mail archive of the
cygwin-patches
mailing list for the Cygwin project.
Re: [1.7] Case-sensitive programs exist but cannot both be run
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-patches at cygwin dot com
- Date: Fri, 16 Oct 2009 12:02:10 +0200
- Subject: Re: [1.7] Case-sensitive programs exist but cannot both be run
- References: <4AD7F017.5080609@users.sourceforge.net> <20091016080302.GO27964@calimero.vinschen.de> <4AD832FB.2050901@users.sourceforge.net> <4AD8393C.6040805@lysator.liu.se>
- Reply-to: cygwin-patches at cygwin dot com
On Oct 16 11:13, Peter Rosin wrote:
> Den 2009-10-16 10:46 skrev Yaakov (Cygwin/X):
>> On 16/10/2009 03:03, Corinna Vinschen wrote:
>>> On Oct 15 23:01, Yaakov S wrote:
>>>> It appears that two EXEs can coexist (with the registry setting) but
>>>> only
>>>> whichever one was so named first will be run:
>>>> [...]
>>>> Bug? Limitation? If it hurts, don't do that?
>>>
>>> Limitation. While we can do everything with files using native NT
>>> calls, we can't use NtCreateProcess to create new processes. We
>>> have to use CreateProcess, and there's no flag available which defines
>>> case-sensitivity for this call, unfortunately.
>>
>> In that case, let's document it. Patch attached.
>
> *snip*
>
>> +trying to run either of them will always run whichever was so named
>> first.
>
> I suspect that you don't necessarily get the one which was named first. My
> guess is that you'll get whichever file happening to appear first in the
> unsorted directory list. Seems bad to make "promises" in the docs in this
> case...
Something along the lines of "there's no way to determine which one of
it will be started since starting applications is still case-insensitive
due to WIndows limitations" might make sense.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat