Improving ext4: bigalloc, inline data, and metadata checksums
Posted Dec 1, 2011 19:36 UTC (Thu) by nix
In reply to: Improving ext4: bigalloc, inline data, and metadata checksums
Parent article: Improving ext4: bigalloc, inline data, and metadata checksums
I shouldn't respond to this troll-bait, but nonetheless...
The big problem with 'ext4' is that its only reason to be is to allow Red Hat customers to upgrade in place existing systems, and what Red Hat wants, Red Hat gets (also because they usually pay for that and the community is very grateful).
Interesting. tytso wasn't working for RH when ext4 started up, and still isn't working for them now. So their influence must be more subtle.
I also see that I was making some sort of horrible mistake by installing ext4 on all my newer systems, but you never make clear what that mistake might have been.
In particular JFS should have been the "default" Linux filesystem instead of ext for a long time. Not making JFS the default was probably the single worst strategic decision for Linux (but it can be argued that letting GKH near the kernel was even worse).
Ah, yeah. Because stable kernels, USB support, mentoring newbies, the driver core, -staging... all these things were bad
I've been wracking my brains and I can't think of one thing Greg has done that has come to public knowledge and could be considered bad. So this looks like groundless personal animosity to me.
to post comments)