public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael C. de Almeida" <almeidaraf@gmail.com>
To: "Mihai Donțu" <mihai.dontu@gmail.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, "Fred ." <eldmannen@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Please add ZFS support (from GPL sources)
Date: Thu, 17 Jul 2008 23:03:30 -0300	[thread overview]
Message-ID: <487FF9F2.5000906@gmail.com> (raw)
In-Reply-To: <200807180133.19191.mihai.dontu@gmail.com>

Mihai Donțu wrote:
> On Thursday 17 July 2008, H. Peter Anvin 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
>>  From what I can see, it is an absolutely-minimal readonly implementation.
> 
> There are a number of fs drivers in the kernel which provide read-only 
> support. The GPL-ed code might not be much (I haven't looked at it), but if 
> someone would spend some time to write a nice, clean patch which can be 
> easily improved, I think there would be at least one user out there who would 
> find it useful.
> 
> Of course, this could open a door for all kinds of incomplete drivers, but 
> these days people seem nuts about ZFS.
> 
> In second thoughts, maybe a fuse based driver would be better. :)
> 

I think there's already work being done for zfs on fuse
(http://www.wizy.org/wiki/ZFS_on_FUSE). Not sure how it's going, though.

  reply	other threads:[~2008-07-18  2:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17 19:13 Please add ZFS support (from GPL sources) Fred .
2008-07-17 18:55 ` Alan Cox
2008-07-17 19:28 ` H. Peter Anvin
2008-07-17 22:33   ` Mihai Donțu
2008-07-18  2:03     ` Rafael C. de Almeida [this message]
2008-07-18 12:27       ` Patrick Draper
2008-07-18 10:28   ` Matthias Schniedermeyer
2008-07-17 19:30 ` Alexey Dobriyan
2008-07-17 19:45 ` 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
     [not found] <89239e000807230040l7491478fy2ed6a43f9f2fcdb7@mail.gmail.com>
2008-07-23  7:46 ` Chen Zheng

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=487FF9F2.5000906@gmail.com \
    --to=almeidaraf@gmail.com \
    --cc=eldmannen@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mihai.dontu@gmail.com \
    /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