605
this post was submitted on 06 Sep 2024
605 points (90.3% liked)
linuxmemes
20751 readers
268 users here now
I use Arch btw
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Windows and NTFS support case sensitive filenames. The functionality is disabled for compatibility reasons.
And you can enable it: https://learn.microsoft.com/en-us/windows/wsl/case-sensitivity
I 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.
What happens if i put case sensitive files into an ntfs pendrive and plugged into windows?
Windows sees both files
Can it rename it then? What happens if cd into a folder from cmd with same name?
Windows gets confused, I don't remember what exactly happens.
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.
You can create files with the same name differing only by case through WSL. I've had issues with it before.
I remember the good old days of Windows MS-DOS where they had an 8 character filename limit lol
8.3, actually!
Gotta go count my files again... oh yeah it's PROJE~14.BAS
haha 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
~1thing!Funnily enough you can have up to 65536 files in a directory in FAT, so you could technically end up with PR~65536.BAS