From: Diego Calleja <diegocg@gmail.com>
To: Hector Martin <hector@marcansoft.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Coding FATX support for 2.6
Date: Mon, 24 Sep 2007 00:25:13 +0200 [thread overview]
Message-ID: <20070924002513.f11d1546.diegocg@gmail.com> (raw)
In-Reply-To: <46F6D1C3.2070208@marcansoft.com>
El Sun, 23 Sep 2007 16:51:15 -0400, Hector Martin <hector@marcansoft.com> escribió:
> Most xbox-linux users are stuck using 2.4, since there is no FATX driver
> for 2.6 and the 2.4 one is unmaintained. I've been thinking about
> writing FATX support into 2.6, to finally end this problem (this is
> basically the only thing holding up 2.6 for Xbox Linux distros). While I
> have done a little kernel coding in the past, I've never messed with
> filesystems in Linux and I'm not entirely sure what the best approach
> would be here. I would like to do it in such a way that it can be
FUSE could be an acceptable solution.
next prev parent reply other threads:[~2007-09-23 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-23 20:51 Coding FATX support for 2.6 Hector Martin
2007-09-23 22:25 ` Diego Calleja [this message]
2007-09-23 22:34 ` Hector Martin
2007-09-24 7:05 ` Christoph Hellwig
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=20070924002513.f11d1546.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=hector@marcansoft.com \
--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