> You can use FreeBSD, they are happy to provide
I'd stop at that.
What's going on here is that people on the internet are asking Greg K-H to do extra work and his reply is that he doesn't care to.
If anything what is childish is random internet users thinking that they are entitled to Linux dev's time and work.
That really isn't "what's going on here." The "extra work" is changing one or two lines from containing EXPORT_SYMBOL_GPL to EXPORT_SYMBOL and possibly moving them to a different place.
If you read through the email thread [1] linked in another comment, you'll see something completely different is being argued and discussed.
Last I heard, the Linux Kernel was under the GPL and needs to comply with that. Is "follow a contract I opted into" fundamentalism/militancy?
The GPL is a licence that was created by people well-aware of the political significance, and it is the embodiment of certain political intentions in form of a licence. Projects that consciously use it can be expected to act upon those political intentions. Not understanding actions upon those political intentions is rather a sign of not understanding the situation.
Though I could have sworn the controversy was about __kernel_fpu becoming kernel_fpu - is there another set of git commits I need to find and rollback/reverse engineer on my 4.19 branch?
If a patch for zfs shows up in some random github repo that correctly teaches it to use the gpl-only symbols? I hope it makes it into your hands.
Anyway you can always patch the kernel. It won't be as easy to install, but e.g. Ubuntu should be able to do so.
That's a big accusation.
Do you have any evidence?
I love ZFS, use it on my server. It sucks that this has happened but AFAICT it's the result of a license choice made way back when, and it's still impacting things now.