From: Daniel Hazelton <dhazelton@enter.net>
To: David Lang <david.lang@digitalinsight.com>
Cc: "Tomasz Kłoczko" <kloczek@rudy.mif.pg.gda.pl>,
"Matthew Garrett" <mjg59@srcf.ucam.org>,
"Theodore Tso" <tytso@mit.edu>,
"David R. Litwin" <presently42@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: ZFS with Linux: An Open Plea
Date: Tue, 17 Apr 2007 18:52:29 -0400 [thread overview]
Message-ID: <200704171852.29546.dhazelton@enter.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0704171505390.1696@qynat.qvtvafvgr.pbz>
On Tuesday 17 April 2007 18:12:17 David Lang wrote:
> On Tue, 17 Apr 2007, Daniel Hazelton wrote:
> > On Tuesday 17 April 2007 15:58:09 Tomasz Kłoczko wrote:
> >> On Tue, 17 Apr 2007, Daniel Hazelton wrote:
> >> [..]
> >>
> >>>> Why on discussion about switching to GPL v3 Linux code this argument
> >>>> was allways taken as "piece of cake". Why in case switching to another
> >>>> license which will allow use CDDL code just it is most importand contr
> >>>> argument ?
> >>>>
> >>>> kloczek
> >>>
> >>> Because *EVERY* version of the GPL contains the "or any later version
> >>> of this license" clause (except, now, the version being used with the
> >>> Linux kernel)
> >>
> >> So after around commented swiching to GPL v3 it will be possible to
> >> start work on GLP v3.5 which will allow easy reuse CDDL code under Linux
> >> .. good to know :o)
> >
> > Nope. Note that I said "Except the Linux Kernel".
> >
> > After the discussions that took place back around the time of the release
> > of the first draft of GPLv3 it was decided to lock Linux to *ONLY* GPLv2
>
> actually the GPLv2 only predates the GPLv3 draft by several years
>
> there are quite a few other projects that are also GPLv2 only
>
> > So the Linux kernel will *never* be able to have a version of the GPL
> > other than the current one applied. This change might have occurred
> > without the knowledge or agreement of the FSF, who maintain the GPL, but
> > since it was done with the complete agreement of all the current
> > developers - and assumed agreement of any who contributed and are no
> > longer able to consent (since their code was originally released under
> > GPLv2) - it should stand. After all, the form of the license that applies
> > to the kernel is shipped with the kernels sources.
>
> the 'or later' version is not part of the GPLv2 license itself, it's a burb
> that the FSF suggests that people use so that they (the FSF) can
> retroactivly change the license of the code that other people create.
>
> The dispute over the GPLv3 is if these retroactive chagnes aer to the
> benifit or detriment of the people who created the code.
>
> > In fact, from the copy in the latest Git:
> > NOTE! This copyright does *not* cover user programs that use kernel
> > services by normal system calls - this is merely considered normal use
> > of the kernel, and does *not* fall under the heading of "derived work".
> > Also note that the GPL below is copyrighted by the Free Software
> > Foundation, but the instance of code that it refers to (the Linux
> > kernel) is copyrighted by me and others who actually wrote it.
> >
> > Also note that the only valid version of the GPL as far as the kernel
> > is concerned is _this_ particular version of the license (ie v2, not
> > v2.2 or v3.x or whatever), unless explicitly otherwise stated.
> >
> > Linus Torvalds
> > -----------------
>
> take a look at the date that this went into the kernel
Yeah, I did afterwards. Perhaps it was because of the discussion that occurred
then that I remember it.
> >> How many years it will take ? two, three ? more ? (it will be
> >> good to know how long we must wait on ZFS under Linux .. I don't belive
> >> in rewriting ZFS code time and make it so useable on production as *now*
> >> it is possible under Solaris/*BSD/MOX and passing all pointless arguing
> >> will take shorter time) .. or maybe never because some people says
> >> something like "Linux is in GPL cage".
> >
> > Linux is not in any cage - Solaris and ZFS, because of the CDDL, sit
> > inside the cage. I, personally, will *NEVER* release code meant to be
> > "open source" under a license that makes demands like those of the user.
>
> and similarly, many people will not release code under a license that lets
> other people change the terms years later.
Agreed. This is something that I would never do.
DRH
>
> David Lang
next prev parent reply other threads:[~2007-04-17 22:52 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 6:54 ZFS with Linux: An Open Plea David R. Litwin
2007-04-17 8:18 ` Miklos Szeredi
2007-04-17 13:10 ` Theodore Tso
2007-04-17 13:47 ` Tomasz Kłoczko
2007-04-17 13:59 ` Matthew Garrett
2007-04-17 15:46 ` Tomasz Kłoczko
2007-04-17 15:59 ` Alan Cox
2007-04-17 16:29 ` Daniel Hazelton
2007-04-17 19:58 ` Tomasz Kłoczko
2007-04-17 22:19 ` Daniel Hazelton
2007-04-17 22:12 ` David Lang
2007-04-17 22:52 ` Daniel Hazelton [this message]
2007-04-17 22:38 ` Roland Dreier
2007-04-17 14:06 ` Erik Mouw
2007-04-17 14:32 ` John Anthony Kazos Jr.
2007-04-17 15:41 ` Tomasz Kłoczko
2007-04-17 16:02 ` John Anthony Kazos Jr.
2007-04-17 14:37 ` Diego Calleja
2007-04-17 14:48 ` Alan Cox
2007-04-17 15:06 ` Ricardo Correia
2007-04-17 15:23 ` Xavier Bestel
2007-04-17 15:30 ` Ricardo Correia
2007-04-17 15:36 ` Alan Cox
2007-04-17 16:02 ` Mike Snitzer
2007-04-17 16:57 ` Alistair John Strachan
2007-04-18 11:10 ` Manoj Joseph
2007-04-18 11:23 ` Alan Cox
2007-04-18 11:32 ` Manoj Joseph
2007-04-17 16:22 ` Daniel Hazelton
2007-04-17 17:50 ` Theodore Tso
2007-04-17 19:24 ` Florian Weimer
2007-04-17 19:56 ` Ricardo Correia
2007-04-17 20:05 ` Ricardo Correia
2007-04-17 14:59 ` linux-os (Dick Johnson)
2007-04-17 15:08 ` Xavier Bestel
2007-04-17 15:12 ` linux-os (Dick Johnson)
2007-04-17 15:29 ` Michal Schmidt
-- strict thread matches above, loose matches on Subject: below --
2007-04-17 8:42 David R. Litwin
2007-04-15 8:57 David R. Litwin
2007-04-15 17:34 ` Kasper Sandberg
2007-04-15 8:54 David R. Litwin
2007-04-16 0:50 ` Rik van Riel
2007-04-16 3:07 ` David Chinner
2007-04-14 17:40 Ignatich
2007-04-15 12:44 ` Nikita Danilov
2007-04-17 14:14 ` Alan Cox
2007-04-13 23:18 David R. Litwin
2007-04-13 23:43 ` Neil Brown
2007-04-14 12:16 ` Christoph Hellwig
2007-04-14 14:04 ` Mike Snitzer
2007-04-14 20:53 ` Jan Engelhardt
2007-04-16 9:40 ` Tomasz Kłoczko
2007-04-16 11:19 ` John Anthony Kazos Jr.
2007-04-16 14:02 ` Stefan Richter
2007-04-16 14:20 ` Tomasz Kłoczko
2007-04-16 14:55 ` Christoph Hellwig
2007-04-16 15:46 ` Tomasz Kłoczko
2007-04-16 15:59 ` Christoph Hellwig
2007-04-16 19:02 ` Diego Calleja
2007-04-16 20:18 ` Tomasz Kłoczko
2007-04-18 17:25 ` Lennart Sorensen
2007-04-18 17:39 ` Jeff Garzik
2007-04-27 5:21 ` Valerie Henson
2007-04-27 21:57 ` Matt Mackall
2007-04-16 19:46 ` Jörn Engel
2007-04-16 18:19 ` Stefan Richter
2007-04-16 19:21 ` Bernd Eckenfels
2007-04-16 19:26 ` Lee Revell
2007-04-16 20:20 ` Bernd Eckenfels
2007-04-16 20:15 ` Stefan Richter
2007-04-14 21:13 ` Bill Huey
2007-04-16 9:58 ` Tomasz Kłoczko
[not found] ` <170fa0d20704160507w4af4cb92ua259a55789f95c3e@mail.gmail.com>
2007-04-16 14:01 ` Tomasz Kłoczko
2007-04-16 14:30 ` Adrian Bunk
2007-04-16 15:27 ` Tomasz Kłoczko
2007-04-16 17:21 ` Adrian Bunk
2007-04-14 18:56 ` Krzysztof Halasa
2007-04-16 3:00 ` David Chinner
2007-04-15 4:16 ` Kasper Sandberg
2007-04-15 21:58 ` Jesper Juhl
2007-05-02 15:03 ` Tomasz Kłoczko
2007-05-02 15:42 ` Alan Cox
2007-05-02 20:53 ` Theodore Tso
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=200704171852.29546.dhazelton@enter.net \
--to=dhazelton@enter.net \
--cc=david.lang@digitalinsight.com \
--cc=kloczek@rudy.mif.pg.gda.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=presently42@gmail.com \
--cc=tytso@mit.edu \
/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