Announcement

Collapse
No announcement yet.

Linux 5.2 Will Be A Huge Release: EXT4 Case Insensitive, NVIDIA AltMode, Fieldbus + More

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #21
    Originally posted by anarki2 View Post
    Case sensitive filenames must go. Not because evil M$$$, but because they're stupid. There's literally zero use case for being able to have both filename.txt and fILenAME.txT in the same directory. If you absolutely need something like this, you're most definitely doing it wrong and you're a possible candidate for complete idiot.
    Sorry there is not Zero usage case of case sensitive in this thread 1 was mentioned.
    Originally posted by campbell View Post
    Worth pointing out that the kernel sources themselves still cannot be checked out onto a case-insensitive file system.
    There are cases where you see README.TXT and readme.txt in different packages with one being current to use and 1 being future draft to review. Another one that turns up is file records containing names because you can have two people with same letters in name just with different capitalisation.

    NTFS has added a directory flag to turn on case sensitively/turn off casefold in windows 10 because there are usage cases.

    Reality is there is a need for case insensitive and case sensitive. So neither windows or linux for a long time did not cover all usage cases with file systems perfectly.

    Yes a lot of old unix workloads contained events that required case sensitive.

    Just because something seams stupid does not mean there are not usage cases that are best served by that stupid.


    Comment

    Working...
    X