From: jim owens <jowens@hp.com>
To: Kevin Winchester <kjwinchester@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: Please add ZFS support (from GPL sources)
Date: Mon, 21 Jul 2008 11:17:33 -0400 [thread overview]
Message-ID: <4884A88D.30406@hp.com> (raw)
In-Reply-To: <d1af83620807210740vfef575bp73832fd95d803850@mail.gmail.com>
Kevin Winchester wrote:
>
> On Mon, Jul 21, 2008 at 11:23 AM, Fred . <eldmannen@gmail.com> wrote:
>
>>On Mon, Jul 21, 2008 at 1:39 PM, Kevin Winchester
>>>
>>>No one else seems to have volunteered, so I would certainly like to
>>>give it a try. I guess I need to get the ZFS grub code, create a ZFS
>>>filesystem, and start looking around for information on linux
>>>filesystem development and ZFS (obviously without looking at any CDDL
>>>licensed code).
>>
>>Code can be found here;
>>* http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/grub/grub-0.95/stage2/
>>
>>But it may be covered by patents by Sun. So maybe not allowed make an
>>implementation. :(
>>Maybe you should consult SFLC (Software Freedom Law Center) first or something.
>>
> I would have no idea of the legal implications here. Do I really need
> to get the lawyers involved just to use GPLv2 code from another
> project in linux?
Having just gone through open sourcing with lawyers, I would
say anything with a GPLv2 is safe. Any patent Sun has on things
released under GPLv2 is open for use.
I don't know anything about CDDL rules, but if you don't look at
it, you won't be legally contaminated.
I have not looked at the ZFS grub code, but a general warning
based on my experience with other filesystem bootstrap code
is that it may be very limited and not be able to deal with
all structures on a ZFS filesystem... you won't know until
you hit one of them and fail.
jim
prev parent reply other threads:[~2008-07-21 15:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f188924b0807171213q43f10b09j47b34674fc8aaa38@mail.gmail.com>
2008-07-17 19:45 ` Please add ZFS support (from GPL sources) Jeff Garzik
2008-07-17 20:18 ` Evgeniy Polyakov
2008-07-20 10:57 ` Christoph Hellwig
2008-07-20 12:35 ` Kevin Winchester
2008-07-20 16:56 ` Dave Kleikamp
2008-07-21 7:28 ` Christoph Hellwig
2008-07-21 11:39 ` Kevin Winchester
[not found] ` <f188924b0807210723v3a35de9fgc1565811a0597833@mail.gmail.com>
2008-07-21 14:40 ` Kevin Winchester
2008-07-21 14:50 ` Bernd Petrovitsch
2008-07-22 7:44 ` Christoph Hellwig
2008-07-22 8:15 ` Bernd Petrovitsch
2008-07-21 15:17 ` jim owens [this message]
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=4884A88D.30406@hp.com \
--to=jowens@hp.com \
--cc=kjwinchester@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--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 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).