linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: linuxppc-dev@lists.linuxppc.org, debian-powerpc@lists.debian.org,
	linuxppc-user@lists.linuxppc.org
Cc: dburcaw@terraplex.com, jhaas@madison-web.com
Subject: BootX 1.1.2 in a tarball
Date: Thu, 5 Aug 1999 20:40:41 +0200	[thread overview]
Message-ID: <19990805204041.006632@mail.mipsys.com> (raw)


Ok, I finally followed Brad Midgley suggestion to make a tarball of the
BootX folder copied to a netatalk volume. So you have a tarball
containing all the .AppleDouble stuffs. You can get this back intact on
MacOS (with resource forks, type/creators, ...) only by mounting it over
the network via netatalk. However, you win the ability to read the source
from Linux ;-) (You may still have trouble with MacOS-like carriage
returns, I'll try to fix this for the next minor release).

So welcome http://calvaweb.calvacom.fr/bh40/BootX_1.1.2.tgz ;-)

However, take care of the fact that ordinary MacOS tools like Stuffit are
completely unable to expand those things. The result is usually
unuseable. I hope someone with a bit of MacOS knowledge will find the
time to write a decompression tool for that. I do have the knowledge but
unfortunately not the time :-(

n.b. you may have noticed the cross-postingm, don't reply to all
recipients of this email !

-- 
           Perso. e-mail: <mailto:bh40@calva.net>
           Work   e-mail: <mailto:benh@mipsys.com>
BenH.      Web   : <http://calvaweb.calvacom.fr/bh40/>




[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

                 reply	other threads:[~1999-08-05 18:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=19990805204041.006632@mail.mipsys.com \
    --to=bh40@calva.net \
    --cc=dburcaw@terraplex.com \
    --cc=debian-powerpc@lists.debian.org \
    --cc=jhaas@madison-web.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=linuxppc-user@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).