Remember: GNU/Linux and other UNIX systems can make files that are case-sensitive, Windows can't make files that are case-sensitive
Remember: GNU/Linux and other UNIX systems can make files that are case-sensitive, Windows can't make files that are case-sensitive
![](https://lemmy.world/pictrs/image/e5cb8b7b-dc6a-4911-bcb9-6722ac787144.png?thumbnail=1024&format=webp)
You're viewing a single thread.
Windows and NTFS support case sensitive filenames. The functionality is disabled for compatibility reasons.
53 1 ReplyI remember the good old days of Windows MS-DOS where they had an 8 character filename limit lol
10 0 Reply8.3, actually!
11 0 ReplyGotta go count my files again... oh yeah it's PROJE~14.BAS
5 0 Replyhaha that was so infuriating. if their intent was to bastardize the filename horribly to make it noticeable that you defied the DOS limitation, they certainly succeeded. Yuck, totally forgot about the
~1
thing!5 0 ReplyFunnily enough you can have up to 65536 files in a directory in FAT, so you could technically end up with PR~65536.BAS
5 0 Reply
And you can enable it: https://learn.microsoft.com/en-us/windows/wsl/case-sensitivity
4 0 ReplyI actually really like that fsutil case sensitivity can be set on a folder by folder basis so that I can have a safe space to deal with Linux files.
2 0 Reply
Same on macOS. Apple has "case-sensitive HFS+" as an option for UNIX compatibility (or at least they used to) but actually running a system on it is a bad idea in general.
6 0 ReplyWhat happens if i put case sensitive files into an ntfs pendrive and plugged into windows?
4 0 ReplyWindows sees both files
4 0 ReplyCan it rename it then? What happens if cd into a folder from cmd with same name?
1 0 ReplyWindows gets confused, I don't remember what exactly happens.
0 0 Reply
You can create files with the same name differing only by case through WSL. I've had issues with it before.
2 0 Reply