Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA6125 ; Tue, 05 Jan 93 04:12:42 EST Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!uunet!gatech!destroyer!cs.ubc.ca!uw-beaver!news.tek.com!psgrain!m2xenix!agora!rgrimes From: rgrimes@agora.rain.com (Rodney Grimes) Subject: Re: [386BSD] corrupt files Message-ID: <C0HrHK.AtK@agora.rain.com> Organization: Open Communications Forum References: <56750001@acf3.NYU.EDU> <1993Jan6.043012.53@kumr.lns.com> Date: Thu, 7 Jan 1993 16:08:08 GMT Lines: 36 pozar@kumr.lns.com (Tim Pozar) writes: >chapman@acf3.NYU.EDU (Gary W. Chapman, , ,) writes: >>After downloading 386BSD from agate.berkeley.edu (and from another place >>as well), I get >> >>bin01.02 is corrupt >>bin01.03 is corrupt >> >>when doing 'extract'. What can I do? >>- Gary Chapman, chapman@nyu.edu > Try re-getting the file before it too (ie bin01.01). I have notice >extract will identify the file following a corrupt "bad" when the one >before it was bad (truncated, etc.). The easy way to find out what files are corrupt is to get the Manifest file when you get the bin01.* files, then do the following in the directory that has all the files in it just before you run extract: cksum bin01.* >checksums diff -c Manifest checksums Any files that are bad well show up with bad checksums and/or bad lenghts and cause diff to output a line. If diff reports no errors, extract better not because this is almost exactly what it does to get the error messages bin01.xx is corrupt. > Tim >-- > Internet: pozar@kumr.lns.com FidoNet: Tim Pozar @ 1:125/555 >Snail: Tim Pozar / KKSF / 77 Maiden Lane / San Francisco CA 94108 / USA > Voice: +1 415 788 2022 -- Rod Grimes rgrimes@agora.rain.com Accurate Automation Company All opinions belong to me and my company!