From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <ee9e417a05031207346fbb1ad7@mail.gmail.com>
Date: Sat, 12 Mar 2005 10:34:01 -0500
From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] bunzip2 problem
In-Reply-To: <901a05bc93ca1c6efa4b7a9ea26436c7@terzarima.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <23ade4b72e69e0a7b6eaf67fe52fbffd@comcast.net>
	<901a05bc93ca1c6efa4b7a9ea26436c7@terzarima.net>
Topicbox-Message-UUID: 23a16296-ead0-11e9-9d60-3106f5b1d025

there is a program on unix called bzip2recover
which may or may not be helpful in getting some
of your data back.  you can build it on plan9 with
cd /sys/src/cmd/bzip2; mk 8.bzip2recover.

russ


On Sat, 12 Mar 2005 12:36:28 +0000, Charles Forsyth
<forsyth@terzarima.net> wrote:
> 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.
>
>