From: Dan Bethe <dan_bethe@yahoo.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: hfs resource forks in Linux
Date: Mon, 13 Sep 1999 12:05:25 -0700 (PDT) [thread overview]
Message-ID: <19990913190525.5485.rocketmail@web1006.mail.yahoo.com> (raw)
Hi guys. In another thread, I saw someone ask for technique to
sensibly manage HFS resource forks in Linux. Here are the following
two tools I've known. 'hfstools' is pretty flexible, and will do
encoding conversions (macbinary, binhex, etc) on the fly. Tons of
options available in that one. I dont know about hfsutils-devel other
than that it's a C library, and the rpm I found was only for i386 but
it's obviously got the docs.
I'm not sure if this is suitable for any advanced or particular use
other than general file management, but it's all I know. I found these
on www.linuxnow.com's search engine.
ftp://ftp.varesearch.com/pub/mirrors/redhat/roughcuts/ppc/SRPMS/hfsutils-3.2-1b.src.rpm
ftp://ftp.varesearch.com/pub/mirrors/redhat/redhat/powertools/5.2/i386/hfsutils-devel-3.2-1.i386.rpm
===
"We can learn from the past, but those days are gone.
We can hope for the future, but there may not be one."
-- http://www.dreamtheater.net/songb5.htm#VI1
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-09-13 19:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-13 19:05 Dan Bethe [this message]
1999-09-13 20:30 ` hfs resource forks in Linux Martin Costabel
1999-09-13 20:44 ` Tom Rini
1999-09-13 20:37 ` Daniel Jacobowitz
1999-09-14 9:15 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
1999-09-13 21:47 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=19990913190525.5485.rocketmail@web1006.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).