From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bunzip2 problem
Date: Sat, 12 Mar 2005 12:36:28 +0000 [thread overview]
Message-ID: <901a05bc93ca1c6efa4b7a9ea26436c7@terzarima.net> (raw)
In-Reply-To: <23ade4b72e69e0a7b6eaf67fe52fbffd@comcast.net>
i can't advise about the decompression failure, but
you get the strange messages because bunzip2 uses %r
but the error was an internal one, and %r prints the last
system error for the process, which was the shell exec
searching . before /bin for a suitable bunzip2 when
you invoked it. thus, the text after ``can't write...:'' isn't
relevant to the underlying problem.
next prev parent reply other threads:[~2005-03-12 12:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 12:24 Gregory Pavelcak
2005-03-12 12:36 ` Charles Forsyth [this message]
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=901a05bc93ca1c6efa4b7a9ea26436c7@terzarima.net \
--to=forsyth@terzarima.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).