Re: Point of gpl-only modules (flame)

[Jan Engelhardt <jengelh@computergmbh.de>]

On Oct 2 2007 23:49, Jimmy wrote:
>
> Anyway, I've been trying to figure out what purpose the gpl-only code serves.
> What good comes out of disabling people from probing modules that do not have a
> gpl-compatible license?

find /lib/modules/`uname -r` -iname '*.ko' | wc -l:

	2021

Proprietary modules that I can think of:

	5 to 10

It's not even 1/2 a !#$ percent. (Though knowing that many modules are for
not-so-common hw.)

> It seems pretty childish to try and force some license on people, imagine
> trying to install firefox on Windows Vista, an error-dialog box appears:
> "This application has been denied access to the Windows API as its license are
> compatible with the Microsoft Philosophy" ?

Not a kernel problem.

(That said, MS would probably face yet another antitrust charge if it did that.
Or better yet, people would just thankfully stop using it.)

> Now, i don't want to waste clock cycles on executing code that serves no
> purpose but restraining me from using my $1500 gfx card as intended,

Perhaps you intended to buy a game console instead?

That said, no one is restraining you. You can edit the kernel source
and rip out all the GPL checks. On top, it's not like the ati or
nvidia blob-ola would not load in today's kernel.

01:00 ichi:~ > lsmod | grep nv
nvidia               4717076  22 

Oh yeah, my kernel (unpatched, btw) really tries to stop me hard
from loading it.

> so will me
> removing that crap from the source result in somebody trying to obfuscate it to
> a point where neither of us know what is what?
>
> Also, how about a list of PROS, explain to me whats so cool about it?
>
> - Jimmy
-
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/