Neither is RMS, though; the license is the text of the GPL, not anything RMS
may have said about it since.
> The GPL is about "the program". As far as I'm concerned, modules are the
> kernel, "the program".
The modules are *not* "the kernel". They are independent (except for header
files, but you didn't make that argument, and it's by no means certain to
hold up in court, especially if you don't use any code from the headers)
pieces of code that happen to interact with the kernel. Why are modules,
from a legal standpoint, different from user programs? And since when are
derivative works under copyright law determined by the opinion of the
copyright holder (much less any random third party that doesn't happen to be
a court), other than to be more lenient than the law requires?
> The way to stem any panic that may exist, if you want to allow binary-only
> modules (which sucks*, but whatever)
Sure, they suck, but only for the users that choose to use them and the
providers of the modules that have to deal with the maintenance issues.
What sucks even more, though, is someone else making the choice for them.
> *How 'bout a nice binary-only Forth running the kernel? Metacompiling
> kernel routines into the Forth dictionary and such. Sound creepy? Good.
The only creepy thing here is the kernel being written in Forth; if you
don't want to run it in that binary-only implementation, find (or write) a
free one that will get the job done. There's no need to get the courts and
lawyers involved, and no need to punish the users of the software by
restricting what they can do.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/