linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: ttabi@interactivesi.com (Timur Tabi)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox), linux-kernel@vger.kernel.org
Subject: Re: Module Licensing?
Date: Wed, 31 Oct 2001 00:25:53 +0000 (GMT)	[thread overview]
Message-ID: <E15yjCb-0001q7-00@the-village.bc.nu> (raw)
In-Reply-To: <3BDF423D.1060503@interactivesi.com> from "Timur Tabi" at Oct 30, 2001 06:13:49 PM

> Ah, but what happens if I distribute the source code, the closed-source .o 
> files, and a makefile, and tell people that they should link it?  Am I 
> violating the GPL, or is the end-user?

I am told by legal people you are, because you provided the code soley with
the intent that it was used that way. Whether an imaginative lawyer can
also get you locked away under the DMCA for distributing a device for
violating copyright I dont know 8)

It is actually all very simple in legal terms. The legal terminology is
"derivative work" and basically if its a derivative work of a GPL work its
GPL if not it isnt. Thats what "linking" is about - not /bin/ld.

If you wanted to provide a mixed source/binary driver that wasnt derivative
of the kernel (and there are lots of reasons for it) - don't GPL your 
open source bit use something like MPL or BSD

[I am not a laywer ...]

Alan


  reply	other threads:[~2001-10-31  0:19 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-30  3:46 Module Licensing? Kevin D. Wooten
2001-10-30  4:08 ` Ben Greear
2001-10-30  4:58   ` TimO
2001-10-30  5:10     ` Ben Greear
2001-10-30  7:24     ` Kevin D. Wooten
2001-10-30 17:27     ` Timur Tabi
2001-10-30 23:10       ` Alan Cox
2001-10-31  0:13         ` Timur Tabi
2001-10-31  0:25           ` Alan Cox [this message]
2001-10-31 16:53             ` Timur Tabi
2001-10-31 17:10               ` Rik van Riel
2001-10-31 17:22                 ` Larry McVoy
2001-10-31 17:27                   ` Rik van Riel
2001-10-31 18:34                     ` Larry McVoy
2001-10-31 18:44                       ` Rik van Riel
2001-10-31 18:53                         ` Andreas Dilger
2001-10-31 20:08                     ` Craig Milo Rogers
2001-10-31 17:32                   ` dean gaudet
2001-10-31 19:55                   ` [OT] " Craig Milo Rogers
2001-10-31 21:42                     ` Cort Dougan
2001-10-31 23:47                       ` Jamie Lokier
2001-10-31 23:54                         ` Larry McVoy
2001-11-01  0:10                           ` Jamie Lokier
2001-11-01  0:43                       ` Alan Cox
2001-11-01 23:52                         ` n0ano
2001-10-31 17:29                 ` Timur Tabi
2001-10-31 17:37                   ` Rik van Riel
2001-10-31 18:31                     ` LLX
2001-11-08  0:36                       ` drizzt.dourden
2001-11-08 12:41                         ` Alan Cox
2001-11-08 13:19                           ` Drizzt Do'Urden
2001-11-08 14:53                             ` Module Licensing? (thinking a little more) Drizzt Do'Urden
2001-11-08 15:56                               ` Doug McNaught
2001-11-08 17:00                                 ` Drizzt Do'Urden
2001-11-08 17:18                                   ` Russell King
2001-11-08 17:47                                     ` Drizzt Do'Urden
2001-11-09  7:50                                       ` Stefan Smietanowski
2001-11-10 18:09                                     ` QuoteMstr - Danny Colascione
2001-11-08 17:29                                   ` Doug McNaught
2001-11-08 19:28                                     ` drizzt.dourden
2001-10-31 20:15                     ` Module Licensing? Craig Milo Rogers
2001-10-31 19:49                 ` Craig Milo Rogers
2001-11-04  3:37                 ` Albert D. Cahalan
2001-10-31 17:11               ` Alan Cox
2001-11-05  4:40       ` [file interface] " Roger Larsson
2001-10-30  9:22 ` 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=E15yjCb-0001q7-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ttabi@interactivesi.com \
    /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).