From: Brad Boyer <flar@pants.nu>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: HFS+ format
Date: Sat, 29 Jan 2000 19:56:36 -0800 (PST) [thread overview]
Message-ID: <200001300356.WAA12189@marcus.pants.nu> (raw)
In-Reply-To: <B4B7C54D.602%pajama1@mindspring.com>
Actually, there is a project to develop an HFS+ filesystem module for Linux.
However, it isn't useful at the moment. There is a small amount of code
available, but it is too much to send in an email, and I don't have a place
to host it. If someone wants to volunteer to host this, I'll stick up a web
page or ftp site with the code and some info. I currently do have it on a
publicly accessible site, but I don't want to flood it because it is on a
slow link to the net. I might give the address to one or two more people
who are really interested, since there are already several of us in the
project.
Currently there is only a basic framework for the VFS interface and some of
the BTree parsing code, but it crashes frequently and can't do anything
useful.
Brad Boyer
flar@pants.nu
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2000-01-30 3:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B4B7C54D.602%pajama1@mindspring.com>
2000-01-30 3:56 ` Brad Boyer [this message]
2000-01-30 13:58 ` HFS+ format Olaf Hering
2000-01-31 4:04 ` devel kernels 2.3.41 ramp
2000-01-31 7:20 ` Martin Costabel
2000-01-31 21:23 ` Kevin M. Myer
2000-01-31 22:22 ` Martin Costabel
2000-02-01 17:18 ` Ani Joshi
2000-01-30 19:21 HFS+ format Dan Bethe
[not found] <20000130101504.11105.qmail@web1004.mail.yahoo.com>
2000-01-30 15:25 ` Brad Midgley
-- strict thread matches above, loose matches on Subject: below --
2000-01-30 2:53 Dan Bethe
2000-01-29 8:29 Dan Bethe
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=200001300356.WAA12189@marcus.pants.nu \
--to=flar@pants.nu \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.