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
On 16/10/2009 05:02, Corinna Vinschen wrote:
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.
Revised patch attached.
Yaakov
2009-10-27 Yaakov Selkowitz <yselkowitz@users.sourceforge.net>
* 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 28 Oct 2009 02:24:10 -0000
@@ -489,10 +489,14 @@
</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,
+starting applications is still case-insensitive due to Windows limitations
+and so the program you try to launch may not be the one actually started. 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