I’d love to hear what people here think of this. I hate proprietary kernel modules, I’m sure most people here do too, so do you think there is legal ground to force proprietary module vendors to release their source code?
My assumption is that it’s not a violation because the module’s code doesn’t contain GPL code but interfaces with the kernel (another program) that is GPL. As long as the sources don’t mix it shouldn’t be an issue, but then I’m not sure about the full technical details.
[…] legal ground to force proprietary module vendors to release their source code?
What would make anyone think that? No one has to publish their code. If you really want a FLOSS kernel you’ll have to find open replacements for those modules or make them yourself.
Actually, if you distribute a derivative work of a GPL licensed project, you have to release the source code.
I have to admit that I’m not all that knowledgeable about licensing, so I did a little research and you are totally right. My bad! Legal means would totally be possible then, but that’d require someone actually pressing charges. Since that hasn’t happened yet, I fear it’s pretty unlikely at least in the foreseeable future…
If you really want a FLOSS kernel you’ll have to find open replacements for those modules or make them yourself.
basically openbsd?
