linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andre Hedrick <andre@linux-ide.org>
To: Pascal Schmidt <der.eremit@email.de>
Cc: David Schwartz <davids@webmaster.com>, linux-kernel@vger.kernel.org
Subject: RE: Driver Model
Date: Wed, 3 Sep 2003 18:37:04 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.10309031836080.13722-100000@master.linux-ide.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0309040049490.5139-100000@neptune.local>


Pascal,

SUPER HIGH FIVE!

You have made the obvious clear, and most will not even follow or listen.

Cheers,

Andre Hedrick
LAD Storage Consulting Group

On Thu, 4 Sep 2003, Pascal Schmidt wrote:

> On Wed, 3 Sep 2003, David Schwartz wrote:
> 
> > If the GPL_ONLY stuff is a license enforcement scheme, the DMCA 
> > prohibits you from removing it.
> 
> -ENOTUSCITIZEN
> 
> > If the GPL_ONLY stuff is not a license enforcement scheme, nothing 
> > prohibits you from stamping your module GPL when it's not.
> 
> I'd say its up to the lawyers and judges to find out whether having
> MODULE_LICENSE("GPL") in a module means anything legally. It might
> mean "I promise this module is made from GPL source", but it might
> also mean nothing.
> 
> > However, the GPL (section 2b) prohibits you from imposing any
> > restrictions other than those in the GPL itself.
> 
> Section 2b) in the file COPYING in the root dir of the kernel source
> does not talk about restrictions. Are we talking about the same version
> of the GPL?
> 
> > The GPL contains no restrictions that
> > apply to mere use and the GPL_ONLY stuff affects use, so it can't be a
> > license restriction, hence there is no restriction to enforce.
> 
> The GPL doesn't even cover use of the "product". It covers modification
> and redistribution.
> 
> Well, it is still an open question whether kernel modules are derived
> works or not, especially since we don't have a stable kernel ABI and
> therefore modules have to use part of the kernel source (headers) and
> module writers have to study kernel code to write their modules (since
> there is no official complete documentation about functions in the 
> kernel).
> 
> If modules are derived works, then legally, following the GPL, they
> must be GPL too and GPL_ONLY is no problem but pointless.
> 
> Seems to me you could say GPL_ONLY is a way of the developer saying
> "I consider your stuff to be a derived work if you use this symbol".
> Ask a lawyer whether that's their decision to make. ;)
> 
> Apart from that, I fail to see how it is an addition restriction
> when you still have the right to remove all the GPL_ONLY stuff. After
> all, the kernel is GPLed work, so you have the right to remove
> things and distribute the result. How is it a real restriction when
> the license allows you to remove it?
> 
> -- 
> Ciao,
> Pascal
> 
> -
> 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/
> 


  parent reply	other threads:[~2003-09-04  1:55 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <rtHg.3n0.9@gated-at.bofh.it>
     [not found] ` <rK5y.1xN.25@gated-at.bofh.it>
2003-09-03 18:42   ` Driver Model 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-10 14:59               ` People, not GPL [was: Re: Driver Model] Timothy Miller
2003-09-10 20:34                 ` David Schwartz
2003-09-12 19:55                   ` Timothy Miller
2003-09-13 14:18                     ` Geert Uytterhoeven
2003-09-13 17:58                       ` Alan Cox
2003-09-10 23:35                 ` James Clark
2003-09-04  1:37         ` Andre Hedrick [this message]
2003-09-02 18:43 Driver Model 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
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

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=Pine.LNX.4.10.10309031836080.13722-100000@master.linux-ide.org \
    --to=andre@linux-ide.org \
    --cc=davids@webmaster.com \
    --cc=der.eremit@email.de \
    --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;
as well as URLs for NNTP newsgroup(s).