Return to BSD News archive
Xref: sserve alt.cd-rom:16797 comp.os.386bsd.questions:10694 Newsgroups: alt.cd-rom,comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!doc.ic.ac.uk!lyra.csx.cam.ac.uk!warwick!uknet!EU.net!uunet!majipoor.cygnus.com!fnf From: fnf@cygnus.com (Fred Fish) Subject: Re: Can't read parts of new FreeBSD 1.1 cd-rom Message-ID: <Cqx00r.6qF@cygnus.com> Organization: Amiga Library Services References: <1994Jun4.213359.328@robkaos.ping.de> <akiyCqwvJL.1Do@netcom.com> Date: Sun, 5 Jun 1994 08:10:02 GMT Lines: 33 In article <akiyCqwvJL.1Do@netcom.com>, Jun Akiyama <akiy@netcom.com> wrote: >The problem is not in your hardware at all. It is our disc at >fault. > >There was a mastering error that caused some corrupted files >in some of the directories (eg /filesys/usr/src/sys/i386/*). >... >We are very, *very* sorry for such an error on our part. We will >try our hardest to never repeat such a mistakes in the future. Just a hint for anyone else making CD-ROM's that would like to avoid similar problems. Before running your mastering software, while the files are still on a hard drive, cd to the root of the file tree and do: find . -type f -print >/tmp/FileList sed "s:^./::" </tmp/FileList >FileList brik -Gvbf FileList >CRCList This will create a CRC check file containing the CRC of every file that will ultimately end up on the CD. Then, at each step of the manufacturing process, you can check the integrity of the files with: brik -Cb CRCList I do this with all my CD-ROM's. It has not only assured me that the files all exist and are correct on the final production CD's, but has uncovered subtle problems with various different 3rd party CD-ROM drivers on the target system (an Amiga) that might have gone unnoticed otherwise, until someone tried to read the particular file that tickled the driver bugs. -Fred