F2FS Will Have Faster Case-Insensitive Lookups With Linux 5.4

[dragon321]

Because all this added complexity open a mostly unnecessary pandora can of bugs. Very few people ever asked for this, and the Linux kernel already has enough random bugs. Make software simpler not over complex at each and every corner.

I think a lot of typical users would want to have this. It's important feature for them. "Simpler" shouldn't mean "less features".

[starshipeleven]

# CONFIG_F2FS_FS is not set

https://bugzilla.opensuse.org/show_bug.cgi?id=1109665

It's also a shitshow on OpenWrt, reliably breaking on anything that isn't x86 or ARM, and on x86 in some cases.

[xorbe]

It's a widely known fact that people on Tumbleweed don't need this.

(more seriously, what are you talking about?)

# CONFIG_F2FS_FS is not set

[starshipeleven]

Because all this added complexity open a mostly unnecessary pandora can of bugs. Very few people ever asked for this, and the Linux kernel already has enough random bugs. Make software simpler not over complex at each and every corner.

This is code that does not affect most other parts of the kernel. At worst, this specific feature is bugged.

[rene]

Funny considering case insensitive is harder to implement than case sensitive. Instead of simply comparing bytes you have to take care of sensitivity. When you have a lot of alphabets (We have Unicode) it's become quite difficult. Really compare with DOS? DOS had filenames with format 8.3, supported only ANSI and wasn't case preserving. Modern implementation (like this on ext4 and F2FS) should support Unicode, be optional and case preserving. If you compare this with DOS you can also compare modern Linux with 70's UNIX.

Another thing: Case insensitive is more natural to typical users and humans at all. Why "Letter.txt" and "letter.txt" should be different things? Why changing character case make some name totally different name? Case sensitivity forces user to think like computer do - file names is not file names but just a string of bytes. If Linux is about freedom why not give case insensitivity to user which wants it instead of trying to make him take different approach with arguments like "Its old Windows/DOS crap don't take it"?

Because all this added complexity open a mostly unnecessary pandora can of bugs. Very few people ever asked for this, and the Linux kernel already has enough random bugs. Make software simpler not over complex at each and every corner.

[tildearrow]

I find it really sill what a fuzz is made here re-occurringly about such an anti-features. Who in it's right mind would want to use such a crippled DOS name lookup thing?

DOS isn't truly case-insensitive. It is always-uppercase.

[starshipeleven]

But not on openSUSE Tumbleweed.

It's a widely known fact that people on Tumbleweed don't need this.

(more seriously, what are you talking about?)

[dragon321]

antiquated implementation detail.

Funny considering case insensitive is harder to implement than case sensitive. Instead of simply comparing bytes you have to take care of sensitivity. When you have a lot of alphabets (We have Unicode) it's become quite difficult. Really compare with DOS? DOS had filenames with format 8.3, supported only ANSI and wasn't case preserving. Modern implementation (like this on ext4 and F2FS) should support Unicode, be optional and case preserving. If you compare this with DOS you can also compare modern Linux with 70's UNIX.

Another thing: Case insensitive is more natural to typical users and humans at all. Why "Letter.txt" and "letter.txt" should be different things? Why changing character case make some name totally different name? Case sensitivity forces user to think like computer do - file names is not file names but just a string of bytes. If Linux is about freedom why not give case insensitivity to user which wants it instead of trying to make him take different approach with arguments like "Its old Windows/DOS crap don't take it"?

[xorbe]

But not on openSUSE Tumbleweed.

[starshipeleven]

Who in it's right mind would want to use such a crippled DOS name lookup thing?

It's situational, mostly for running Windows crap in Wine and file sharing with Samba (that do expect this and at the moment are relying on a more expensive workaround).

Can be useful for any folder that stores only man-created files as most people won't 100% remember the case of all letters in the filenames.


I don't see what there is to be so enraged about. Someone paid someone else to implement it, that's more proof that there is some need, even if niche. (Although I would not call Samba usage "niche" by any stretch of the imagination)