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.
Yaakov
2009-10-16 Yaakov Selkowitz <[email protected]>
* pathnames.sgml: Add limitation of case sensitivity with CreateProcess.
Index: pathnames.sgml
===================================================================
RCS file: /cvs/src/src/winsup/doc/pathnames.sgml,v
retrieving revision 1.46
diff -u -r1.46 pathnames.sgml
--- pathnames.sgml 9 Oct 2009 11:19:18 -0000 1.46
+++ pathnames.sgml 16 Oct 2009 08:43:44 -0000
@@ -489,10 +489,13 @@
</note>
<para>After you set this registry value to 0, Cygwin will be case-sensitive
-by default on NTFS and NFS filesystems. Be aware that using two filenames
-which only differ by case might result in some weird interoperability
-issues with native Win32 applications. You're using case-sensitivity
-at your own risk. You have been warned!</para>
+by default on NTFS and NFS filesystems. However, there are limitations:
+while two <emphasis role='bold'>programs</emphasis>
<filename>Abc.exe</filename>
+and <filename>aBc.exe</filename> can be created and accessed like other files,
+trying to run either of them will always run whichever was so named first.
+Also, be aware that using two filenames which only differ by case might
+result in some weird interoperability issues with native Win32 applications.
+You're using case-sensitivity at your own risk. You have been warned! </para>
<para>Even if you use case-sensitivity, it might be feasible to switch to
case-insensitivity for certain paths for better interoperability with
