public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jimmy <lists@dusted.dk>
To: linux-kernel@vger.kernel.org
Subject: Point of gpl-only modules (flame)
Date: Tue, 02 Oct 2007 23:49:04 +0200	[thread overview]
Message-ID: <4702BCD0.4010202@dusted.dk> (raw)

I know I'll be getting hell for this, I must be a masochist.

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?
Of cause, I would love to see more hardware manufactures release either 
full specs, or GPL'd drivers, and I'm sure it will happen, in time.
But until then, why are people wasting time writing code to inhibit 
those who do not agree with them on licensing?

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" ?

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, 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

             reply	other threads:[~2007-10-02 22:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-02 21:49 Jimmy [this message]
2007-10-02 22:58 ` Point of gpl-only modules (flame) Olivier Galibert
2007-10-02 23:01 ` Jan Engelhardt
2007-10-03 11:32   ` linux-os (Dick Johnson)
2007-10-03 16:50     ` David Newall
2007-10-02 23:25 ` Arjan van de Ven
     [not found] <fa.uOYpsaQzzWwjjKspWNuGWwuESHM@ifi.uio.no>
2007-10-04  2:08 ` Robert Hancock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4702BCD0.4010202@dusted.dk \
    --to=lists@dusted.dk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox