From: Brad Boyer <flar@pants.nu>
To: dan_bethe@yahoo.com (Dan Bethe)
Cc: omarvo@hotmail.com (marv), linuxppc-dev@lists.linuxppc.org
Subject: Re: hfs+
Date: Thu, 17 Feb 2000 06:43:26 -0800 (PST) [thread overview]
Message-ID: <200002171443.JAA18824@marcus.pants.nu> (raw)
In-Reply-To: <20000216093709.29255.qmail@web1003.mail.yahoo.com> from "Dan Bethe" at Feb 16, 2000 01:37:09 AM
Dan Bethe wrote:
> Bless you. Lots of people would be grateful. This would be
> tremendously useful, especially if it could be the main crossplatform,
> mature, multiuser, unix-like filesystem to share data between Linux and
> MacOS 8/9/10 on the same machine.
> Beware of duplicate work. There are the hfsutils, which are user
> space utilities. And there is something that's either a library or a
> kernel module, that someone's working on, which is nonfunctional at
> this time.
> Do searches on lists.linuxppc.org to find who's doing what. We've
> recently discussed this within the last 2 months.
> pajama1@mindspring.com and tdilling@oncodev.isc-net.upenn.edu are in
> my linuxppc notes as being interested in hfs+ development.
> Also see this:
>
> http://developer.apple.com/technotes/tn/tn1150.html
>
> --- marv <omarvo@hotmail.com> wrote:
> > Who's working HFS+ and can i help? I know some seem and i've been
> > reading the kernel vfs docs and the hfs+ docs from apple.
> > Reply directly because i was too lazy to join the mailing list
> > although
> > i did browse through the archives :P
I am the one with the mostly non functional code for a kernel filesystem
module for hfsplus. The current code is available in my directory on
devel.linuxppc.org as a patch against a 2.2.14 kernel tree. However, the
big problem now is that the filesystem structure doesn't seem to match
what I got out of the Apple technote, which may be due to an error
on my part or a lack of info from Apple. I haven't had the time to look
into it carefully yet, but if you want to look, I'll do what I can to
help. The URL is http://dev.linuxppc.org/pub/users/flar/ which has
links to individual patches I have posted. The most recent patch as of
this moment can mount a filesystem and has code to read directories and
data forks of files, but sometimes misreads the catalog and loses track
of files at odd times. It isn't likely to damage disks, but it does
crash occasionally and cause strange errors.
Brad Boyer
flar@pants.nu
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-17 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20000216093709.29255.qmail@web1003.mail.yahoo.com>
2000-02-17 3:54 ` hfs+ unit
2000-02-17 14:43 ` Brad Boyer [this message]
2000-02-17 10:53 hfs+ D.J. Barrow
-- strict thread matches above, loose matches on Subject: below --
1999-02-06 7:55 HFS+ nathan ingersoll
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=200002171443.JAA18824@marcus.pants.nu \
--to=flar@pants.nu \
--cc=dan_bethe@yahoo.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=omarvo@hotmail.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;
as well as URLs for NNTP newsgroup(s).