Re: crc when installing comp33.tgz from japanese mirror

["Dom De Vitto" <dom_(_at_)_DeVitto_(_dot_)_com>]

With comp33 it wont stop you doing normal stuff, but you will
eventually find that something is screwed up when you try compiling
something.

Carry on and reboot etc, but redownload comp33 and untar it to /.

If you don't do this you may/will spend days wondering why one app
doesn't compile - and it turns out that some obscure header was corrupt.

Dom
PS. I have had comp32 corrupt myself - I wonder why the comp tarball
seems to like getting screwed up during ftp installs...?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Dom De Vitto                                       Tel. 07855 805 271
http://www.devitto.com                         mailto:dom_(_at_)_devitto_(_dot_)_com
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -


-----Original Message-----
From: owner-misc_(_at_)_openbsd_(_dot_)_org [mailto:owner-misc_(_at_)_openbsd_(_dot_)_org] On Behalf
Of Joel Rees
Sent: Thursday, May 15, 2003 9:26 AM
To: misc_(_at_)_openbsd_(_dot_)_org
Subject: crc when installing comp33.tgz from japanese mirror


Just installed from

    ftp://ftp.jp.openbsd.org/pub/OpenBSD/ 

After ftp finished downloading comp33.tgz, I got the message 

    gzip: stdio: invalid compressed data -- crc error

but it continued on its merry way, made the devices and so forth, and
told me to reboot.

How worried should I be? Should I let this thing boot to see what kind
of dmesg it spits out? Should I just start from scratch with a different
mirror?


-- 
Joel Rees <joel_(_at_)_alpsgiken_(_dot_)_gr_(_dot_)_jp>