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

linuxmemes

21378 readers
1301 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
    •  

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    605
    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 2 months ago by LuuTuyen@lemmy.world to c/linuxmemes@lemmy.world
    239 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 2 months ago* (last edited 2 months 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 2 months 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 2 months 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.