On 7/10/21 21:12, Kari Argillander wrote:
NTFS is case-sensitive filesystem which Windows treats with tricks like
case-insentive.
This is a distinction without a difference. It's not by default case-sensitive,
but it is case-preserving.
Your driver lets me create a file called foo.txt and one called FOO.TXT in a
normal directory, and when I double-click on one in Windows the wrong file gets
opened. That's 100% a bug.
I disagree. NTFS point of view no bug at all. I agree that it maybe
Windows point view might be a bug. I agree that it might be good thing
to add mount option flag to control this behavier. Maybe nicest thing
would be that if we save other file which match case sensitive we just
raise flag for this folder and atleast never Windows will be able handle
those correctly. What do you think about this Konstantin?
Very dangerous. If you did this in System32 say, you could very easily nuke
your boot because Windows was looking for NTOSKRNL.EXE rather than ntoskrnl.exe -
even if that's not the file you were using.
It's worth pointing out that the Linux vfat driver handles case-sensitivity on
Microsoft's other filesystem correctly.
Question: do you disagree with the approach the vfat writers took? And if not,
what's the difference between FAT and NTFS in this regard?
Quite apart from anything else, the principle of least astonishment says that
Linux should follow what the reference implementation does. By all means add
a mount option to force case-sensitivity throughout, but this shouldn't be
the default.
