3 ms·
For reference, NTFS is case-sensitive. Win32 is case-insensitive. The case sensitivity is implemented at a layer above the filesystem so that classic Windows ap
by kevingadd 12y ago
For reference, NTFS is case-sensitive. Win32 is case-insensitive. The case sensitivity is implemented at a layer above the filesystem so that classic Windows apps will behave the way users expect. (Case sensitive filesystems are confusing for users and mostly create opportunities for horrible mishaps.) As a result, the POSIX subsystem can store case sensitive files just like a linux FS would, with 'FOO' and 'foo' being separate files right next to each other:
http://support.microsoft.com/kb/100625 http://support.microsoft.com/kb/100625
Case insensitivity like win32's is still kind of a mess, but it's unfair to paint the developers of NTFS as idiots when they actually got this right. Above the FS layer is the correct place to implement case insensitivity, because case insensitivity is a feature that aids users in selecting files, not a feature that aids applications in opening them or creating them.
- durin42 12y agoI don't know. Now you end up in a circumstance where you have N files named some variant of "Foo" and the GUI layer can't distinguish them. Enforcing this invariant at the filesystem layer (with well defined semantics, which HFS+ at least documents semi-well) seems eminently reasonable to me.