mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: "Andre Hedrick" <andre@linux-ide.org>,
	"James Clark" <jimwclark@ntlworld.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Driver Model
Date: Tue, 2 Sep 2003 17:20:10 -0700	[thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKAENJGCAA.davids@webmaster.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10309021555410.8229-100000@master.linux-ide.org>


	I agree with you, except for the one place where you've contradicted
yourself:

> If you are an embedded space widget.  Apply thumb to nose and wiggle
> fingers.  Provided you ship the source code you modify in the kernel, and
> I do mean all of it, use the short cut to clobber the issues in module.h.
> When they scream and complain about, this violates intent, ask them are
> they issuing a restriction on the usage of the GPL kernel?  If they do not
> permit one to use it under GPL them the kernel itself is in violation.

	In other words, you cannot release something under the GPL and
simultaneously restrict its use.

> Now back to "tainting", if the politics were such to cause all modules
> which are not GPL to be rejected then the game is over.  Because the
> kernel does not reject loading, it by default approves of closed source
> binary modules.  One could use the means of taint-testing to accept or
> reject, regardless of the original intent.  Many have and will make the
> argument the kernel has the ability to reject closed source and it choose
> to accept.

	So no, the kernel does not have the ability to reject closed source. That
would be an additional restriction upon use that the GPL does not allow you
to impose.

	DS



  reply	other threads:[~2003-09-03  0:20 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-02 18:43 James Clark
2003-09-02 19:13 ` Robert Love
2003-09-02 20:44 ` Richard B. Johnson
2003-09-03 14:36   ` Stuart MacDonald
2003-09-03 14:52     ` Jan-Benedict Glaw
2003-09-03 14:57     ` Alan Cox
2003-09-03 15:13       ` Stuart MacDonald
2003-09-03 15:33         ` Mariusz Zielinski
2003-09-03 15:50           ` Stuart MacDonald
2003-09-03 16:02             ` Mariusz Zielinski
2003-09-03 17:58               ` Stuart MacDonald
2003-09-03 16:58             ` Alan Cox
2003-09-03 18:21               ` Jeff Garzik
2003-09-03 15:50           ` Mariusz Zielinski
2003-09-03 22:41       ` David Schwartz
2003-09-04 11:03         ` Alan Cox
2003-09-03 15:22     ` Richard B. Johnson
2003-09-02 21:29 ` Patrick Mochel
2003-09-02 21:44   ` James Clark
2003-09-02 22:05     ` Greg KH
2003-09-02 22:08     ` Robert Love
2003-09-02 22:39     ` Jamie Lokier
2003-09-02 23:52 ` Andre Hedrick
2003-09-03  0:20   ` David Schwartz [this message]
2003-09-03 17:38     ` Andre Hedrick
2003-09-03 18:19       ` Alan Cox
2003-09-03 18:15         ` Andre Hedrick
2003-09-04 12:40       ` Henning P. Schmiedehausen
2003-09-03 13:10 ` Alan Cox
     [not found] <rtHg.3n0.9@gated-at.bofh.it>
     [not found] ` <rK5y.1xN.25@gated-at.bofh.it>
2003-09-03 18:42   ` Pascal Schmidt
2003-09-03 19:49     ` Andre Hedrick
2003-09-03 22:41     ` David Schwartz
2003-09-03 23:11       ` Pascal Schmidt
2003-09-03 23:33         ` David Schwartz
2003-09-04  1:38           ` Pascal Schmidt
2003-09-04  3:01             ` David Schwartz
2003-09-04 14:21               ` Pascal Schmidt
2003-09-04  1:37         ` Andre Hedrick

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=MDEHLPKNGKAHNMBLJOLKAENJGCAA.davids@webmaster.com \
    --to=davids@webmaster.com \
    --cc=andre@linux-ide.org \
    --cc=jimwclark@ntlworld.com \
    --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

Powered by JetHome