linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kevin Winchester" <kjwinchester@gmail.com>
To: "Christoph Hellwig" <hch@infradead.org>
Cc: "Jeff Garzik" <jeff@garzik.org>, "Fred ." <eldmannen@gmail.com>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Please add ZFS support (from GPL sources)
Date: Mon, 21 Jul 2008 08:39:14 -0300	[thread overview]
Message-ID: <d1af83620807210439r6b8fa39bu4f3fd76c86aa548d@mail.gmail.com> (raw)
In-Reply-To: <20080721072801.GA6115@infradead.org>

On Mon, Jul 21, 2008 at 4:28 AM, Christoph Hellwig <hch@infradead.org> wrote:
> On Sun, Jul 20, 2008 at 09:35:45AM -0300, Kevin Winchester wrote:
>> If Fred declines, is anyone free to take you up on the offer?  I have
>> no filesystem experience and almost no experience with kernel code in
>> general, so I would not be anyone's first choice for a task like this.
>>  However, since it mainly appears to be an integration exercise (using
>> the code from GRUB and making it work in linux), it might well be
>> doable for me.  As a bonus, being highly inexperienced, I have no
>> expectations of doing anything correctly, and thus would not react
>> badly to lots of criticism.
>>
>> So to summarize - if anyone else would like to undertake this work,
>> they probably should.  But if no one has the time/will, then I would
>> be happy to give it a try.
>
> Yes, this offer is of course up to everyone interested.  But it's not
> purely an integration effort in the traditional sense, the grub
> filesystem interface is quite different from the Linux one, and the code
> structure and style is quite different.  But if you're willing to learn
> it should be very interesting.
>

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).

Once I get a handle on that, I'll see where I can get before I need to
ask a thousand questions.

-- 
Kevin Winchester

  reply	other threads:[~2008-07-21 11:39 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 [this message]
     [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=d1af83620807210439r6b8fa39bu4f3fd76c86aa548d@mail.gmail.com \
    --to=kjwinchester@gmail.com \
    --cc=eldmannen@gmail.com \
    --cc=hch@infradead.org \
    --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).