TFI says:
"The FSF, stewards of the GPL, have stated many times over the past decades that they believe there is no legal distinction between dynamic and static linking of a C program and we agree. Accordingly, the analysis is quite obvious to us: if ZFS were statically linked with Linux and shipped as a single work, few would argue it was not a “work based on the Program” under GPLv2."
And that's where it all falls apart. How do we know that it's not a "mere aggregation". See http://www.gnu.org/licenses/gp... which argues that determining whether a separate module is a covered work is actually a tricky question requiring some thought and analysis.
Slashdot Mirror
TFI says: "The FSF, stewards of the GPL, have stated many times over the past decades that they believe there is no legal distinction between dynamic and static linking of a C program and we agree. Accordingly, the analysis is quite obvious to us: if ZFS were statically linked with Linux and shipped as a single work, few would argue it was not a “work based on the Program” under GPLv2." And that's where it all falls apart. How do we know that it's not a "mere aggregation". See http://www.gnu.org/licenses/gp... which argues that determining whether a separate module is a covered work is actually a tricky question requiring some thought and analysis.