[lkml]   [2001]   [Oct]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: GPLONLY kernel symbols???
In mailing-lists.linux-kernel, Pierre-Philippe Coupard wrote:

> The kernel doesn't actually do anything with the "tainted" flag,
> insmod does. So you have to compile things as module and insmod
> them, and insmod will dump a message if the MODULE_LICENSE thing
> isn't in the module. If you compile things inside the kernel instead
> of modules, you will see nothing and /proc/sys/kernel/tainted will
> contain 0, which is wrong.

I think the idea is that if you compile something inside the kernel,
you have the source, so at least from the debugging point of view, the
kernel has not been tainted by a binary-only module.

It seems like people (collectively) have two different purposes in
mind for /proc/sys/kernel/tainted: ensuring that only "open source"
modules are used, for debugging purposes, and ensuring that only
"GPL-compatible" modules are used, for possible legal purposes. If
both of these are desirable, perhaps the two purposes should be
separated into two /proc files?

Cheers, Wayne

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.078 / U:0.476 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site