Re: Point of gpl-only modules (flame)

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Jan Engelhardt
Date: Tuesday, October 2, 2007 - 4:01 pm

On Oct 2 2007 23:49, Jimmy wrote:

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.)


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.)


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.

-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Point of gpl-only modules (flame), Jimmy, (Tue Oct 2, 2:49 pm)
Re: Point of gpl-only modules (flame), Olivier Galibert, (Tue Oct 2, 3:58 pm)
Re: Point of gpl-only modules (flame), Jan Engelhardt, (Tue Oct 2, 4:01 pm)
Re: Point of gpl-only modules (flame), Arjan van de Ven, (Tue Oct 2, 4:25 pm)
Re: Point of gpl-only modules (flame), linux-os (Dick Johnson), (Wed Oct 3, 4:32 am)
Re: Point of gpl-only modules (flame), David Newall, (Wed Oct 3, 9:50 am)