Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!uunet!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!destroyer!news.iastate.edu!help.cc.iastate.edu!michaelv From: michaelv@iastate.edu (Michael L. VanLoon) Subject: Re: How to check Checksums? Message-ID: <michaelv.711730149@help.cc.iastate.edu> Sender: news@news.iastate.edu (USENET News System) Organization: Iowa State University, Ames IA References: <NEAL.92Jul21085411@neal.ctd.comsat.com> Date: Tue, 21 Jul 1992 14:49:09 GMT Lines: 35 In <NEAL.92Jul21085411@neal.ctd.comsat.com> neal@neal.ctd.comsat.com (Neal Becker) writes: >Maybe this is a stupid question. I got bin01.00-bin01.56, ftp'd 'em >to a pc, put 'em on floppies, took 'em home. Then I'm told bin01.11 >is corrupt. Major dissapointment! >How can I check the checksums in the MANIFEST on my unix machine at >work *before* I transferring to my PC? Two other people pointed out the probable cause of this. I was having this problem also. It kept telling me bin01.12 and .13 were corrupt. So, I'd rm them and go back to school and download them again and still corrupt. But, it wasn't the files themselves that were corrupt. What it was seeing was a bad spot on the hard drive that the files were sitting over. For some reason, the stripped down utils on the dist.fs disk didn't see the bad spot, just the corrupted file. The fix is this: 1) Load all the bin01 files to the /tmp dir (if they're not already there). 2) Do NOT rm the file. Rename it: mv bin01.11 bad.bin01.11. That way it will hold the bad spot on your hard disk so nothing else gets put there. 3) Simply reread bin01.11 to the /tmp dir, like this: mread a:bin01.11 /tmp 4) Run extract again. If it complains about another file being corrupt, repeat the procedure for that file. Good luck and hope this fixes your problem. -- ------------------------------------------------------------------------------ Michael L. VanLoon "Ignorance is bliss..." michaelv@iastate.edu -- Computer Engineering, Iowa State University ------------------------------------------------------------------------------