Re:GPL Violations Related to Combining ZFS and Linux
by rando3826 on Thursday February 25, 2016 @04:59PM
(#11178170)
Because canonical wants to be the os of light weight vm images and docker images. You can't do that if the first step in distribution is always "boot into a separate filesystem, compile a kernel module, then reboot", and then if you want to distribute your image to anyone outside your organization, be sure to first remove that kernel module, and have them do the same process again.
[ Parent
| on HN ]
Re:GPL Violations Related to Combining ZFS and Linux
by xenophonf on Thursday February 25, 2016 @06:08PM
(#11178586)
The engineering problems are tractable even in those cases: Don't put the root file system on ZFS. Develop some kind of first-boot initrd that includes enough of a toolchain to build zfs.ko. I'm sure there are other, better ways to solve shipping ZFS in a virtual machine image, especially compared that to the legal and business risks of having a LTS release deemed a copyright infringement: Court costs, legal fees, fines, re-releasing Ubuntu, etc.