linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Rene Herman <rene.herman@gmail.com>
Cc: William D Waddington <william.waddington@beezmo.com>,
	Helge Hafting <helge.hafting@aitel.hist.no>,
	linux-kernel@vger.kernel.org, Al Boldi <a1426z@gawab.com>,
	Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: Please release a stable kernel Linux 3.0
Date: Thu, 28 Jun 2007 23:48:07 +0100	[thread overview]
Message-ID: <20070628234807.4c446062@the-village.bc.nu> (raw)
In-Reply-To: <46842F7B.1010105@gmail.com>

On Fri, 29 Jun 2007 00:00:27 +0200
Rene Herman <rene.herman@gmail.com> wrote:

> On 06/28/2007 06:30 PM, Alan Cox wrote:
> 
> > Public domain is GPL compatible.
> 
> Would you happen to have an opinion on the attached? I don't so much need it 

The answer is "NO!!!!"

Public domain also means "I don't have to give you the source".
If its merged with the kernel the resulting work is GPL anyway

> Stating that code which one intends to be in the public domain has "GPL and 
> additional rights" is a bit of a travesty though.

Indeed if its public domain you may have almost no rights at all
depending what you were given. Once you get the source code you can do
stuff but I don't have to give you that. If its public domain I can find
security holes in it, and refuse to provide the fixed module in source
form even.

(And public domain is a pretty 'brave' choice of licence as in many
countries it does not imply any of the no warranty stuf the GPL does).

So essentially, if its public domain and you put a copy in the kernel GPL
the kernel copy. It doesn't mean the PD version ceased to be PD. If you
want to keep it PD then also ask that anyone contributing to the GPL
version also sends you a PD version of any changes. (They may not but
then right now they dont have to anyway)

Alan

  reply	other threads:[~2007-06-28 22:42 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.ZV8hYZHQHqzfx1dgOFeEVFRogSg@ifi.uio.no>
2007-06-27 14:15 ` Please release a stable kernel Linux 3.0 Bill Waddington
2007-06-28 11:15   ` Helge Hafting
2007-06-28 15:28     ` William D Waddington
2007-06-28 16:30       ` Alan Cox
2007-06-28 16:39         ` William D Waddington
2007-06-29  0:00           ` Alan Cox
2007-06-28 21:39         ` Al Viro
2007-06-28 22:00         ` Rene Herman
2007-06-28 22:48           ` Alan Cox [this message]
2007-06-28 22:45             ` Rene Herman
     [not found] <8AH0j-3Qc-11@gated-at.bofh.it>
     [not found] ` <8AH0j-3Qc-9@gated-at.bofh.it>
     [not found]   ` <8B0vZ-r6-5@gated-at.bofh.it>
     [not found]     ` <8B46G-69z-15@gated-at.bofh.it>
     [not found]       ` <8B52G-7C9-5@gated-at.bofh.it>
     [not found]         ` <8BalK-7Ic-39@gated-at.bofh.it>
     [not found]           ` <8BaYr-8tJ-17@gated-at.bofh.it>
2007-06-29 21:05             ` Bodo Eggert
2007-06-29 21:27               ` Rene Herman
2007-06-30  2:11                 ` Daniel Hazelton
2007-06-30 10:50                   ` Rene Herman
2007-06-27 13:53 Al Boldi
2007-06-27 15:52 ` Adrian Bunk
2007-06-27 16:08   ` Chuck Ebbert
2007-06-27 16:26     ` Dmitry Torokhov
2007-06-27 16:26     ` Adrian Bunk
2007-06-27 22:32   ` Al Boldi
2007-06-27 17:11 ` Al Viro
2007-06-27 22:32   ` Al Boldi
2007-06-27 23:12     ` Al Viro
2007-06-28 15:37       ` Al Boldi
  -- strict thread matches above, loose matches on Subject: below --
2007-06-21 21:49 Zoltán HUBERT
2007-06-21 21:54 ` Chuck Ebbert
2007-06-21 22:08 ` Alan Cox
2007-06-21 22:21   ` Zoltán HUBERT
2007-06-22 20:54     ` Willy Tarreau
2007-06-21 22:29 ` Jesper Juhl
2007-06-21 22:34   ` Chuck Ebbert
2007-06-21 23:01     ` Lennart Sorensen
2007-06-21 23:08       ` Chuck Ebbert
2007-06-21 23:36         ` Måns Rullgård
2007-06-21 23:45         ` Arjan van de Ven
2007-06-28 21:15           ` Pavel Machek
2007-06-29 13:41             ` Rafael J. Wysocki
2007-06-29 22:33               ` Pavel Machek
2007-06-22 15:00     ` Rafael J. Wysocki
2007-06-22 17:11       ` Chuck Ebbert
2007-06-22 22:10         ` Rafael J. Wysocki
2007-06-24 20:54         ` Rafael J. Wysocki
2007-06-25 16:38           ` Chuck Ebbert
2007-06-25 23:20             ` Rafael J. Wysocki
2007-06-25 23:23               ` Chuck Ebbert
2007-06-21 22:57   ` Zoltán HUBERT
2007-06-21 23:07     ` Jesper Juhl
2007-06-21 23:23     ` Lennart Sorensen
2007-06-22  8:34     ` Bernd Petrovitsch
2007-06-26 11:59     ` Helge Hafting
2007-06-26 14:37       ` Zoltán HUBERT
2007-06-26 15:04         ` Renato S. Yamane
2007-06-26 19:03         ` Roland Kuhn
2007-06-27  9:18           ` Zoltán HUBERT
2007-06-27  9:54             ` Alan McKinnon
2007-06-27  9:55             ` Al Viro
2007-06-27 14:44             ` Helge Hafting
2007-06-27 16:13             ` Chuck Ebbert
2007-06-29 16:37             ` Gerhard Mack
2007-06-21 23:30   ` Jan Engelhardt
2007-06-21 23:32     ` david
2007-06-22  8:41       ` Jan Engelhardt
2007-06-21 22:52 ` Stefan Richter
2007-06-21 22:59   ` Zoltán HUBERT
2007-06-21 22:58 ` Rene Herman
2007-06-22  3:51 ` Rik van Riel
2007-06-22  9:19 ` Xavier Bestel
2007-06-22  9:45   ` Bernd Petrovitsch
2007-06-23  7:25 ` Chris Snook

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=20070628234807.4c446062@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=a1426z@gawab.com \
    --cc=helge.hafting@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rene.herman@gmail.com \
    --cc=rusty@rustcorp.com.au \
    --cc=william.waddington@beezmo.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).