JehanneOS/newlib
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

* pathnames.sgml: Rephrase the "Case sensitive filenames" chapter

Browse Source 
slightly.
This commit is contained in:
Corinna Vinschen
2009-02-03 09:03:18 +00:00
parent 42ef1b8fd4
commit f01ffdd1e5
2 changed files with 22 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
winsup/doc/ChangeLog
View File

@@ -1,3 +1,8 @@
2009-02-03 Corinna Vinschen <corinna@vinschen.de>
* pathnames.sgml: Rephrase the "Case sensitive filenames" chapter
slightly.
2009-01-24 Corinna Vinschen <corinna@vinschen.de> 2009-01-24 Corinna Vinschen <corinna@vinschen.de>
* pathnames.sgml: Add requirement for world-readability of special * pathnames.sgml: Add requirement for world-readability of special

34
winsup/doc/pathnames.sgml
View File

@@ -314,7 +314,7 @@ only differ by case, like <filename>Abc</filename> and
<filename>aBc</filename>. While NTFS (and some remote filesystems) <filename>aBc</filename>. While NTFS (and some remote filesystems)
support case-sensitivity, the NT kernel starting with Windows XP does support case-sensitivity, the NT kernel starting with Windows XP does
not support it by default. Rather, you have to tweak a registry setting not support it by default. Rather, you have to tweak a registry setting
and reboot. For that reason, case-sensitivity is not supported by Cygwin, and reboot. For that reason, case-sensitivity can not be supported by Cygwin,
unless you change that registry value.</para> unless you change that registry value.</para>
<para>If you really want case-sensitivity in Cygwin, you can switch it <para>If you really want case-sensitivity in Cygwin, you can switch it
@@ -329,11 +329,12 @@ this registry value also on Windows NT4 and Windows 2000, which usually
both don't know this registry key. If you want case-sensitivity on these both don't know this registry key. If you want case-sensitivity on these
systems, create that registry value and set it to 0. On these systems systems, create that registry value and set it to 0. On these systems
(and *only* on these systems) you don't have to reboot to bring it (and *only* on these systems) you don't have to reboot to bring it
into effect.</para> into effect, rather stopping all Cygwin processes and then restarting them
is sufficient.</para>
<note> <note>
<para> <para>
Note that when installing Microsoft's Services For Unix (SFU), you're asked if When installing Microsoft's Services For Unix (SFU), you're asked if
you want to use case-sensitive filenames. If you answer "yes" at this point, you want to use case-sensitive filenames. If you answer "yes" at this point,
the installer will change the aforementioned registry value to 0, too. So, if the installer will change the aforementioned registry value to 0, too. So, if
you have SFU installed, there's some chance that the registry value is already you have SFU installed, there's some chance that the registry value is already
@@ -351,21 +352,20 @@ at your own risk. You have been warned!</para>
case-insensitivity for certain paths for better interoperability with case-insensitivity for certain paths for better interoperability with
native Win32 applications (even if it's just Windows Explorer). You can do native Win32 applications (even if it's just Windows Explorer). You can do
this on a per-mount point base, by using the "posix=0" mount option in this on a per-mount point base, by using the "posix=0" mount option in
/etc/fstab, or your /etc/fstab.d/$USER file.</para> <filename>/etc/fstab</filename>, or your <filename>/etc/fstab.d/$USER</filename>
file.</para>
<para>For a start, it might be best to switch the cygdrive path to <para><filename>/cygdrive</filename> paths are case-insensitive by default.
case-insensitivity, because the default Windows $PATH variable is not The reason is that the native Windows %PATH% environment variable is not
always using the correct case by default. As a result, your shell will always using the correct case for all paths in it. As a result, if you use
claim that it can't find Windows commands like <command>attrib</command> case-sensitivity on the <filename>/cygdrive</filename> prefix, your shell
or <command>net</command>. Here's an example how you can switch the might claim that it can't find Windows commands like <command>attrib</command>
cygdrive prefix to case-insensitivity:</para> or <command>net</command>. To ease the pain the <filename>/cygdrive</filename>
path is case-insensitive by default and you have to use the "posix=1" setting
<example id="mount-caseinsensitive"> explicitely in <filename>/etc/fstab</filename> or
<title>Example mount point to enforce case-insensitivity on cygdrive paths</title> <filename>/etc/fstab.d/$USER</filename> to switch it to case-sensitivity,
<screen> or you have to make sure that the native Win32 %PATH% environment variable
none /cygdrive cygdrive binary,posix=0 0 0 is using the correct case for all paths throughout.</para>
</screen>
</example>
<para>Note that mount points as well as device names and virtual <para>Note that mount points as well as device names and virtual
paths like /proc are always case-sensitive! The only exception are paths like /proc are always case-sensitive! The only exception are