From: Christoph Hellwig <hch@infradead.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: "Fred ." <eldmannen@gmail.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Please add ZFS support (from GPL sources)
Date: Sun, 20 Jul 2008 06:57:24 -0400 [thread overview]
Message-ID: <20080720105724.GA8921@infradead.org> (raw)
In-Reply-To: <487FA143.9010109@garzik.org>
On Thu, Jul 17, 2008 at 03:45:07PM -0400, Jeff Garzik wrote:
> Fred . wrote:
>> Previously we have not been able to have ZFS support due to it being
>> licensed under the CDDL and the kernel under the GPL.
>>
>> Sun have contributed ZFS support to GRUB under the GPL license. We
>> could now use that code to implement support for ZFS in the Linux
>> kernel.
>>
>> http://blogs.sun.com/darren/entry/zfs_under_gplv2_already_exists
>
> Linux needs btrfs upstream more than it needs ZFS...
Don't be so harsh. Adding a read-only for the start zfs driver for
Linux would be useful for various purposes. And adding read-only
filesystems to Linux is really easy. So if Fred really cares about it
I'd be very happy to mentor him implementing it. IT should be a very
good learning exercise for him.
next prev parent reply other threads:[~2008-07-20 10:57 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 [this message]
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
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=20080720105724.GA8921@infradead.org \
--to=hch@infradead.org \
--cc=eldmannen@gmail.com \
--cc=jeff@garzik.org \
--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).