[lkml]   [2001]   [Oct]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: GPLONLY kernel symbols???
Arjan van de Ven wrote:
> It's not legal issues.

Of course it is, this is code that deals with
whether or not the kernel has loaded something
that's not covered under the GPL license.

> It's 1 integer and 1 sysctl variable that allow
> easy filtering of nvidia and other bugreports.
> THAT is the purpose of "tainted". Show in the oops
> that binary only modules are used.

Then that's the wrong purpose : instead, oops
posters should be made aware that they should
post the list of loaded modules as well. If you
really insist on having the kernel deal with this,
make the kernel print the list of modules as well
as the oops.

(this assumes all gpl modules to have a
MODULE_LICENSE() line which doesn't result in code
and isn't loaded into kernel memory;

Yes it is : what about the code that allows me
to cat /proc/sys/kernel/tainted and echo an integer
into it ? and the code that's not loaded into kernel
memory sure takes storage space, even if it's not

But that's not the point : the point is, the kernel
should contain as much non-kernel junk as possible.
Kernel code, even a small amount of it, that deals
with licensing is junk code. It's silly enough to
have "sponsored by" strings in the kernel as it is.

(@ @)
Pierre-Philippe Coupard
Senior Software Engineer, Lineo, Inc.
(801) 426-5001 x 208

There are many intelligent species in the universe, and they all own
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:08    [W:0.090 / U:0.684 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site