libs/newlib-cygwin
libs
/
newlib-cygwin
mirror of git://sourceware.org/git/newlib-cygwin.git
4
0
Fork 0
Code Issues Projects Releases Wiki Activity

* pathnames.sgml: Add limitation of case sensitivity with CreateProcess.

This commit is contained in:
Corinna Vinschen 2009-10-28 10:11:22 +00:00
parent 641ba32982
commit 757ee9af8b
2 changed files with 12 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
winsup/doc/ChangeLog
View File

@ -1,3 +1,7 @@
2009-10-28 Yaakov Selkowitz <yselkowitz@users.sourceforge.net>
* pathnames.sgml: Add limitation of case sensitivity with CreateProcess.
2009-10-28 Corinna Vinschen <corinna@vinschen.de> 2009-10-28 Corinna Vinschen <corinna@vinschen.de>
* new-features.sgml (ov-new1.7-posix): Mention UTF-8 as "C" default * new-features.sgml (ov-new1.7-posix): Mention UTF-8 as "C" default

12
winsup/doc/pathnames.sgml
View File

@ -489,10 +489,14 @@ set to case sensitivity.
</note> </note>
<para>After you set this registry value to 0, Cygwin will be case-sensitive <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 by default on NTFS and NFS filesystems. However, there are limitations:
which only differ by case might result in some weird interoperability while two <emphasis role='bold'>programs</emphasis> <filename>Abc.exe</filename>
issues with native Win32 applications. You're using case-sensitivity and <filename>aBc.exe</filename> can be created and accessed like other files,
at your own risk. You have been warned!</para> 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 <para>Even if you use case-sensitivity, it might be feasible to switch to
case-insensitivity for certain paths for better interoperability with case-insensitivity for certain paths for better interoperability with