From: Gregory Pavelcak <g.pavelcak@comcast.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] bunzip2 problem
Date: Sat, 12 Mar 2005 07:24:50 -0500 [thread overview]
Message-ID: <23ade4b72e69e0a7b6eaf67fe52fbffd@comcast.net> (raw)
Hello all,
I'm afraid I may have done something wrong in creating a .tbz file, and
now I'm unable to unzip it. I'm hoping there's something I can do to
recover. Here, from memory, is what I did.
I was running Plan 9 in vmware on Windows XP. From /mail/box, I did
tar cf p9mail.tar glenda. that seemed to work and gave me a tar file. I
then decided to bzip2 it since I was going to send it over the net I
figured I'd make it smaller, so bzip2 p9mail.tar gave me p9mail.tbz.
Then, I used cifs to get access to our local Windows server and copied
the file over there. Here's the brilliant step. It didn't occur to me
to confirm that I could unzip the thing before replacing my
Windows/Plan 9 setup with FreeBSD. Since then, I tried to bunzip the
file from BSD (I don't remember the messages from there, but it
failed.) and on my Plan 9 box at home. Here's what I get
cpu% bunzip2 p9mail.tbz
bunzip2: decompress failed
bunzip2: can't write p9mail.tar: './bunzip2' file does not exist
I've also tried bunzip2 using -c and redirection, and it still fails.
I don't understand the './bunzip2' file does not exist" complaint. Just
for the heck of it, I did "touch bunzip2" in the directory where I was
trying to bunzip and got
cpu% bunzip2 p9mail.tbz
bunzip2: decompress failed
bunzip2: can't write p9mail.tar: exec header invalid
I suppose this isn't much to go on. I'm assuming that I did something
wrong in making the file or that something bizarre happened in the cifs
copy. Can I recover this somehow? It contains stored emails and an
outbox from work.
Thanks.
Greg
next reply other threads:[~2005-03-12 12:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 12:24 Gregory Pavelcak [this message]
2005-03-12 12:36 ` Charles Forsyth
2005-03-12 15:34 ` Russ Cox
2005-03-13 9:09 ` Steve Simon
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=23ade4b72e69e0a7b6eaf67fe52fbffd@comcast.net \
--to=g.pavelcak@comcast.net \
--cc=9fans@cse.psu.edu \
/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).