All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Jari Ruusu <jariruusu@users.sourceforge.net>
Cc: Fruhwirth Clemens <clemens@endorphin.org>,
	James Morris <jmorris@redhat.com>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"David S. Miller" <davem@redhat.com>
Subject: Re: Linux 2.6.8-rc3 - BSD licensing
Date: Fri, 6 Aug 2004 09:39:00 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0408060918320.24588@ppc970.osdl.org> (raw)
In-Reply-To: <411353B3.B8748556@users.sourceforge.net>



On Fri, 6 Aug 2004, Jari Ruusu wrote:
> 
> Linus, you are mixing two completely different rights here;
> re-distribution right and re-licensing right.

Ehh.. You're wrong.

Copyright law has nothing to do with "licensing". In fact, if you actually 
read copyright law, you will find that the _only_ thing that it's about is 
the right to distribute a work and the right to make derived works.

(Side note: there are also certain "right of attribution" etc, but that's
still not about re-licensing and those are about the author, not the owner
of the copyright).

In other words, being the "owner" of a work has nothing to do with the
right to "relicence".

Being able to license somebody else to distribute the work does NOT 
require ownership. It only requires a _license_ to do so. You can keep 
owning your copyright, and let somebody else distribute the copy for you 
by liccensing him to do that.

And a license like the BSD license that allows very broad rights to 
_everybody_ means that pretty much everybody can not only distribute it, 
but since the BSD license doesn't even limit how they re-distribute it, 
you can distribute it with some additional requirements of your own.

Why do you think Microsoft etc can take BSD code and then slap their EULA 
on it? Right. They were given the right to distribute. 

> Original license grants
> you GPL-compatible re-distribution rights, which means that the code can
> be distributed and linked with GPL code just fine.

You clearly do not know what you're talking about.

You haven't even read the GPL, have you?

The GPL doesn't say "you can link this with a GPL-compatible license". It 
says:

    b) You must cause any work that you distribute or publish, that in
    whole or in part contains or is derived from the Program or any
    part thereof, to be licensed as a whole at no charge to all third
    parties under the terms of this License.

Notice? It says "this License". Not "this license or some more permissive 
license".

The ONLY license you can use to create a GPL derivative is the GPL itself.

And the way "GPL-compatible" licenses work is _exactly_ because these 
licenses are "weaker" than the GPL, and as such can always be _relicensed_ 
as the GPL.

THAT IS WHAT GPL-COMPATIBLE MEANS!

So when you claim that the code isn't GPL-compatible, and at the same time 
claim that we can't re-license it under the GPL, you are very very 
confused indeed. Either it is GPL-compatible, or it is not. And if it is 
GPL-compatible, that ABSOLUTELY means that it can be relicensed under the 
GPL.

Comprende?

Anyway, the point is moot.  We've removed the code you touched, and I'm
about to apply the new version that is based on Gladman's code (I did the
conversion myself, and James Morris did the final stuff and the
integration with the rest of the code).

And we did that not for legal reasons, but because quite frankly, I don't 
want to have _anything_ to do with somebody as confused as you are. 

			Linus

  reply	other threads:[~2004-08-06 16:42 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-03 22:09 Linux 2.6.8-rc3 Linus Torvalds
2004-08-04 12:07 ` Jan De Luyck
2004-08-04 12:13   ` Karol Kozimor
2004-08-04 12:40   ` Erik Mouw
2004-08-05 15:10     ` OGAWA Hirofumi
2004-08-05 22:19       ` szonyi calin
2004-08-04 12:57   ` Gene Heskett
2004-08-04 12:44 ` Juergen Stuber
2004-08-04 13:37   ` Geert Uytterhoeven
2004-08-04 15:04 ` Jari Ruusu
2004-08-04 16:00   ` James Morris
2004-08-04 16:10     ` J. Bruce Fields
2004-08-04 16:27       ` Arjan van de Ven
2004-08-04 18:19         ` Patrick McFarland
2004-08-04 18:45           ` Linus Torvalds
2004-08-05 13:54             ` Patrick McFarland
2004-08-04 21:27         ` H. Peter Anvin
2004-08-04 18:37     ` Linux 2.6.8-rc3 - BSD licensing Fruhwirth Clemens
2004-08-04 18:51       ` Linus Torvalds
2004-08-04 19:26         ` Fruhwirth Clemens
2004-08-04 19:56           ` Linus Torvalds
2004-08-05 12:33             ` Jari Ruusu
2004-08-05 16:50               ` Linus Torvalds
2004-08-05 17:45                 ` Måns Rullgård
2004-08-05 20:21                   ` Alan Cox
2004-08-05 21:37                     ` Måns Rullgård
2004-08-05 21:08                       ` Alan Cox
2004-08-06  9:47                 ` Jari Ruusu
2004-08-06 16:39                   ` Linus Torvalds [this message]
2004-08-07 10:19                     ` Jari Ruusu
2004-08-07 10:38                       ` Patrick McFarland
2004-08-07 17:27                       ` Linus Torvalds
2004-08-05 12:32     ` Linux 2.6.8-rc3 Jari Ruusu
2004-08-04 16:23   ` Linus Torvalds
2004-08-05 15:04     ` [PATCH] Drop asm i586 AES code James Morris
2004-08-04 15:08 ` Linux 2.6.8-rc3 (compile stats) John Cherry
2004-08-04 18:52 ` [patch] 2.6.8-rc3: fix modular kernel with gcc 2.95 Adrian Bunk
2004-08-06 19:57 ` 2.6.8-rc3: MPT Fusion compile error with PROC_FS=n Adrian Bunk

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.58.0408060918320.24588@ppc970.osdl.org \
    --to=torvalds@osdl.org \
    --cc=clemens@endorphin.org \
    --cc=davem@redhat.com \
    --cc=jariruusu@users.sourceforge.net \
    --cc=jmorris@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.