From: Bernd Petrovitsch <bernd@firmix.at>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Fred ." <eldmannen@gmail.com>,
Kevin Winchester <kjwinchester@gmail.com>,
Jeff Garzik <jeff@garzik.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: Please add ZFS support (from GPL sources)
Date: Tue, 22 Jul 2008 10:15:58 +0200 [thread overview]
Message-ID: <1216714558.14148.31.camel@spike.firmix.at> (raw)
In-Reply-To: <20080722074453.GA25205@infradead.org>
On Tue, 2008-07-22 at 03:44 -0400, Christoph Hellwig wrote:
> On Mon, Jul 21, 2008 at 04:50:54PM +0200, Bernd Petrovitsch wrote:
> > On Mon, 2008-07-21 at 11:40 -0300, Kevin Winchester wrote:
> > [....]
> > > > 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.
That was quoted from a reply since that didn't make it in my mailbox
(and perhaps on the list as the "Cc: added" suggests).
> > Since basically *you* wanted that feature in the first place (and for
> > whatever reason do not even start to work on it),
>
> Either you or I have lost track here. Fred without a lastname asked for
> ZFS support based on the grub code, and never replied again in this
ACK.
To summarize:
- First he requests that someone else implements/ports/... something
(for whatever reason) to GPL/the kernel/....
- Then some advice, hints and a kind soul offers help (no problem for
me).
- And then the original requester comes up with "you might have check
for potential patent problems" on technical mailinglist (at least
most
of the time;-).
The following open questions for me were/are:
- Why is *that* important for the original requester?
- Why didn't he do his (legal) homework before or simply ignore that or
- at least - stated it in the original mail[0].
- Which aspect/unresolved problem/potential problem will come next?
> thread. Kevin volunteered to work on it.
I have no problem with that.
Heck, personally I don't have a problem if someone takes the ZFS source
and makes a (completely separate) GPLv2 patch to use it in kernel-space
(and not "only" with FUSE).
The legal implications?
Apart from the generic lawyer answer "it depends on the circumstances",
I don't know.
Bernd
[0]: What's the English phrase for the German "Salami-Taktik"? You don't
come up with the whole problem at once but try to solve it in
small
steps luring the problem solver (which gets only the next step
presented) into it so that s/he can't stop (for whatever reason
-
it is heavily used in the commercial world).
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
next prev parent reply other threads:[~2008-07-22 8:16 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 [this message]
2008-07-21 15:17 ` jim owens
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=1216714558.14148.31.camel@spike.firmix.at \
--to=bernd@firmix.at \
--cc=eldmannen@gmail.com \
--cc=hch@infradead.org \
--cc=jeff@garzik.org \
--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).