this post was submitted on 06 Sep 2024
608 points (90.3% liked)

linuxmemes

20707 readers
1008 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
poopsmith@lemmy.world
zephyr@lemmy.world
608
Remember: GNU/Linux and other UNIX systems can make files that are case-sensitive, Windows can't make files that are case-sensitive (lemmy.world)
submitted 1 week ago by LuuTuyen@lemmy.world to c/linuxmemes@lemmy.world
242 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] SpaceCadet@feddit.nl 0 points 1 week ago* (last edited 1 week ago) (1 children)

give me one use case where it makes sense having several files with the same name but different cases in the same directory

Imagine a table in a database where the primary key is a case sensitive character field, because you know varchars, just like C char types and string types in other languages are case sensitive.

Imagine a database administrator does the following:

  • Export all data with primary key = 'Abcde' to 'Abcde.csv'

Imagine a second database adminstrator around the same time does the following:

  • Export all data with primary key = 'abcde' to 'abcde.csv'

Now imagine this is the GDPR data of two different users.

If you have a case insensitive file system, you've just overwritten something you shouldn't have and possibly even leaked confidential data.

If you have a case sensitive file system you don't have to account for this scenario. If the PK is unique, the filename will be unique, end of story.

[–] wizardbeard@lemmy.dbzer0.com 0 points 1 week ago (1 children)

If you don't do something stupid like reuse keys just with different capitalization, this never occurs.

[–] SpaceCadet@feddit.nl 5 points 1 week ago

The point is you have to take this into account, so the decision to go with a case insensitive file system has ripple effects much further down your system. You have to design around it at every step in code where a string variable results in a file being written to or read from.

It's much more elegant if you can simply assume that a particular string will 1-on-1 match with a unique filename.

Even Microsoft understands this btw, their Azure Blob Storage system is case sensitive. The only reason NTFS isn't (by default) is because of legacy. It had to be compatible with all uppercase 8.3 filenames from DOS/FAT16.