Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!news.dacom.co.kr!bofh.dot!usenet.seri.re.kr!bofh.dot!news.cais.net!rtd.com!dgy From: dgy@rtd.com (Don Yuniskis) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Questions Questions Questions! Damn I'm frustrated trying to get FreeBSD optimized for my needs Date: 14 Jun 1996 11:52:03 GMT Organization: CICDO Lines: 20 Message-ID: <4prjp3$aib@baygull.rtd.com> References: <31adfe7c.14012906@news.panix.com> <4p25d2$n21@uriah.heep.sax.de> NNTP-Posting-Host: seagull.rtd.com In article <4p25d2$n21@uriah.heep.sax.de>, J Wunsch <joerg_wunsch@uriah.heep.sax.de> wrote: >push@panix.com (SeVeN) wrote: > >> Now just 1 last complain, WALNUT CREEK! BURN YER CDs PROPERLY! I got >> errors on some files on the cd which could not uncompress >> properly. sysinstall tells me the archive is corrupt. >8( > >If it's really a CD-ROM error, return it for a replacement! I suspect it's an intermittent thing. My CD-ROM does this routinely (though I suspect it's somewhere in the scsi subsystem or cd9660 code that's choking). Read some nice huge files off the CD-ROM to purge the offending file(s) from the cache and then try again. This routinely works for me -- especially when building ports and getting complaints about lousy Makefiles (which were actually read incorrectly off the CD) OK, Joerg, time to get back to work! :>