On Wed, 2019-01-16 at 21:27 +0000, WordPress wrote:
Adding a note from last week's meeting -- I think the consensus was that ZFS and a custom kernel (we think that's required?) were not something the editors felt we should strongly promote in Fedora, since it means the kernel taint flag is set. Can this be rethought with another compression option?
The kernel does not have to be recompiled, but a module (zfs.ko) does. The module, when loaded, does indeed taint the kernel. Here is the line that displays in my dmesg output:
znvpair: module license CDDL taints kernel.
There is a "zfs-fuse" package available in the Fedora repositories and a quick online search appears to show that it can be used to boot a zfs root ( https://groups.google.com/forum/#!topic/zfs-fuse/Pngazp3mALw). But the solution looks a bit too hackish for my taste.
Here is an explanation of why zfs-fuse package is is allowed in Fedora, but zfs.ko is not: http://warpmech.com/?news=myth-busting-series-zfs-on-linux-has-license-probl...
Btrfs was mentioned as a possibility, but I am a little weary of it. It looks like RHEL is also deprecating it: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/htm...
It looks like there is a possibility that Oracle may someday change the ZFS license: https://www.phoronix.com/scan.php?page=news_item&px=Oracle-ZFS-2017-Poss...
My intention at the moment is to hold off on doing netboot pt. 5 and maybe revisit the issue if Oracle does update the ZFS license.
Thanks.