From: Benjamin Herrenschmidt <bh40@calva.net>
To: Daniel Jacobowitz <drow@false.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: hfs resource forks in Linux
Date: Tue, 14 Sep 1999 11:15:20 +0200 [thread overview]
Message-ID: <19990914111520.021034@mailhost.mipsys.com> (raw)
In-Reply-To: <19990913163755.A310@them.org>
On Mon, Sep 13, 1999, Daniel Jacobowitz <drow@false.org> wrote:
>Not quite what I was talking about. These let us touch the resource
>fork, and deal with hfs volumes, not manage a specific file's resource
>fork on the resource level.
The resource fork format is not terribly complex. If noone does it, I'll
look into writing a couple of tools for managing them one of those days.
--
Perso. e-mail: <mailto:bh40@calva.net>
Work e-mail: <mailto:benh@mipsys.com>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-09-14 9:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-13 19:05 hfs resource forks in Linux Dan Bethe
1999-09-13 20:30 ` Martin Costabel
1999-09-13 20:44 ` Tom Rini
1999-09-13 20:37 ` Daniel Jacobowitz
1999-09-14 9:15 ` Benjamin Herrenschmidt [this message]
-- 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=19990914111520.021034@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=drow@false.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 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.