> had read that it was suppose to be for maintainability (.i.e. source
> available so kernel gods can debug) and not to enforce ideological
> conformity. Now I read that anything not licensed under the GPL, including
> BSD or simply public domain source code, will taint my kernel and modprobe
> complains about non-GPL stuff including parport_pc which apparently did not
> have a license. Should I expect a Linux kernel KGB to show up next?
Hardly. Its there to handle maintainability issues. Right now its got some
glitches - and the BSD one is a glitch we need to sort out. Clearly BSD
stuff where the source is in the kernel is not harming anyones ability to
deubg.
> Furthermore I have to agree with the previous poster. Any module could
> easily lie to MODULE_LICENSE about its licensing terms and that would not
> make it's source automatically "free" and GPLable so I am now wondering if
> this tainting mechanism is of any use at all.
Well under the DMCA thats probably a criminal offence with five years in
jail. The truth however is that if you want to lie about licensing or run a
modutils that doesn't do it nobody stops you. Its there primarily to deal
with bug filtering from people who don't know better. Folks who know enough
to subvert the mechanism generally also know better than to post Nvdriver
bugs to l/k.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Oct 15 2001 - 21:00:34 EST