Well, the default NTFS mount option is "NT style", meaning that it is
case-insensitive, while still supporting the Basic Multilingual Plane
of ISO-10646 (i.e. Unicode). An NTFS volume provides a special file
that defines what "upper case" is.
> What sort of case-insensitivity do various filesystems currently support?
> Are we talking A-Z only, Latin1, or what? I guess we don't really need to
> worry about what could theoretically be the worst case, but what MS-DOS,
> NT, OS/2 etc actually do right now..
At the moment, it seems most users of the NTFS driver prefer the
following approach:
- Present all files as-is on readdir. NTFS is case preserving, so if
some NT application creates a mixed-case file, it will appear mixed-case
on Linux.
- On lookup, accept any spelling of the file name. This makes
"Makefile" and "makefile" indistinguishable, even though both could
reside in one directory. With the "posix" mount option, you get the
behaviour you are used to.
Please note that this is unrelated to the truncated 8.3 names which
are also available. NTFS defines them as true hard links, and they are
presented as such on Linux. Because those are often all upper-case,
some users prefer them to be converted to all lower-case, so the
completion in the shell works better. The default mount option is to
suppress them in readdir if a full name is available as well.
Regards,
Martin