From: Nix <nix@esperi.org.uk>
To: Tarkan Erimer <tarkane@gmail.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>, linux-kernel@vger.kernel.org
Subject: Re: Sun's ZFS and Linux
Date: Sun, 20 Nov 2005 23:39:08 +0000 [thread overview]
Message-ID: <87r79a7uub.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <9611fa230511201312r5f43e8ady7023b4bde170596e@mail.gmail.com> (Tarkan Erimer's message of "20 Nov 2005 21:12:42 -0000")
On 20 Nov 2005, Tarkan Erimer yowled:
> On 11/19/05, Theodore Ts'o <tytso@mit.edu> wrote:
>> That wouldn't be a "port", it would have to be a complete
>> reimplementation from scratch. And, of course, of further concern
>> would be whether or not there are any patents that Sun may have filed
>> covering ZFS. If the patents have only been licensed for CDDL
>> licensed code, then that won't help a GPL'ed covered reimplementation.
>
> Thanks for the explanation. BTW, I wonder something: Is there any
> possibility to give GPL an exception to include and/or link to CDDL
> code?
You'd have to get agreement from *all* the kernel's past
contributors. As some of them are dead this is not likely to happen.
(Well, OK, you could isolate their code and rewrite it but this
would be a big and annoying job, so you'd need a very compelling
reason. One extra filesystem isn't likely to be good enough.)
--
`Y'know, London's nice at this time of year. If you like your cities
freezing cold and full of surly gits.' --- David Damerell
next prev parent reply other threads:[~2005-11-20 23:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 23:38 Sun's ZFS and Linux Tarkan Erimer
2005-11-19 17:23 ` Theodore Ts'o
2005-11-20 21:12 ` Tarkan Erimer
2005-11-20 23:39 ` Nix [this message]
2005-11-21 17:24 ` Rob Landley
2005-11-21 18:48 ` Jeff V. Merkey
2005-11-21 19:43 ` Tarkan Erimer
2005-11-21 10:11 ` Bernd Petrovitsch
2005-11-21 20:40 ` Bill Davidsen
2005-11-22 14:56 ` Theodore Ts'o
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=87r79a7uub.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tarkane@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 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.