> ignore these and accept a tainted kernel
That isn’t possible as I understand it.
Loading any non-GPL module will mark the Kernel as tainted, but that’s not the issue here.
The problem is that the ZFS module uses Kernel symbols that are marked as GPL-only, meaning that the Kernel will refuse to load the ZFS module as it isn’t marked as a GPL module. There isn’t any way to bypass this short of recompiling the Kernel to remove this restriction.
The legal status of this is uncertain, since a number of questions naturally arise:
1. Is it acceptable to mark a Kernel module as a GPL module (this is done via a macro in the source) but release it under a license that is not GPL-compatible?
2. Is it acceptable to recompile the Kernel to remove this restriction?
As far as I know neither of these have ever been tested, and there are differing opinions.
That isn’t possible as I understand it.
Loading any non-GPL module will mark the Kernel as tainted, but that’s not the issue here.
The problem is that the ZFS module uses Kernel symbols that are marked as GPL-only, meaning that the Kernel will refuse to load the ZFS module as it isn’t marked as a GPL module. There isn’t any way to bypass this short of recompiling the Kernel to remove this restriction.
The legal status of this is uncertain, since a number of questions naturally arise:
1. Is it acceptable to mark a Kernel module as a GPL module (this is done via a macro in the source) but release it under a license that is not GPL-compatible?
2. Is it acceptable to recompile the Kernel to remove this restriction?
As far as I know neither of these have ever been tested, and there are differing opinions.