From: flar@pants.nu (Brad Boyer)
To: linuxppc-dev@lists.linuxppc.org
Cc: linux-fsdevel@vger.kernel.org
Subject: HFS+ support (read-only)
Date: Thu, 6 Jun 2002 05:24:43 -0700 [thread overview]
Message-ID: <20020606052443.A21838@pants.nu> (raw)
I've just uploaded a new release of my hfsplus module. If anyone
would like to try it out, or critique my code, you can find it
on Sourceforge (I am currently using 2.4.18-pre7 as a base):
http://www.sourceforge.net/projects/linux-hfsplus/
This is still read-only, and no resource forks in any format,
but it can handle most standard UNIX features other than
hard links, which will show up as empty files. (Don't ask...)
I haven't had any stability problems, but the performance is
somewhat slow on a disk with a large number of files.
I appreciate any feedback or suggestions.
Brad Boyer
flar@allandria.com
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-06-06 12:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 12:24 Brad Boyer [this message]
2002-06-06 21:23 ` HFS+ support (read-only) Ethan Benson
2002-06-06 22:50 ` Timothy A. Seufert
2002-06-07 7:25 ` Ethan Benson
2002-06-07 19:16 ` Timothy A. Seufert
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=20020606052443.A21838@pants.nu \
--to=flar@pants.nu \
--cc=linux-fsdevel@vger.kernel.org \
--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 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).