From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <901a05bc93ca1c6efa4b7a9ea26436c7@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bunzip2 problem
From: Charles Forsyth <forsyth@terzarima.net>
Date: Sat, 12 Mar 2005 12:36:28 +0000
In-Reply-To: <23ade4b72e69e0a7b6eaf67fe52fbffd@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 238efc00-ead0-11e9-9d60-3106f5b1d025

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.