From: Dan Bethe <dan_bethe@yahoo.com>
To: linuxppc-dev@lists.linuxppc.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: HFS+ format
Date: Sun, 30 Jan 2000 11:21:35 -0800 (PST) [thread overview]
Message-ID: <20000130192135.18931.qmail@web1002.mail.yahoo.com> (raw)
> the best route may be to enhance hfsutils for hfs+ support. you don't have
> to worry about the complexity of multiple readers/writers that way but you
> get a useful, practical result. then jump into writing the kernel code
> after it works satisfactorily.
So you can start with the userspace app and then port that to the kernel? And
is it already GPL? Cool. Who wants to start on that? :^)
=====
"Don't expect your own messiah; this neverworld which you desire is
only in your mind." -- http://www.dreamtheater.net/songb4.htm#IV5
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-01-30 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-30 19:21 Dan Bethe [this message]
[not found] <20000130101504.11105.qmail@web1004.mail.yahoo.com>
2000-01-30 15:25 ` HFS+ format Brad Midgley
[not found] <B4B7C54D.602%pajama1@mindspring.com>
2000-01-30 3:56 ` Brad Boyer
2000-01-30 13:58 ` Olaf Hering
-- 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=20000130192135.18931.qmail@web1002.mail.yahoo.com \
--to=dan_bethe@yahoo.com \
--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).