Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!apple!uokmax!munnari.oz.au!cluster!metro!natmlab.dap.csiro.au!ditsyda!evans From: evans@ditsyda.oz (Bruce Evans) Newsgroups: comp.os.minix Subject: Re: CRC comparisons Message-ID: <2557@ditsyda.oz> Date: 7 Mar 90 20:03:46 GMT References: <8168@sdcc6.ucsd.edu> <18091@rpp386.cactus.org> <789@ns-mx.uiowa.edu> Reply-To: evans@ditsyda.oz (Bruce Evans) Organization: CSIRO DIT Sydney, Australia Lines: 157 I use the following programs (from old postings). 'checkcrc' in particular is very useful for comparing with the official CRC lists. Unfortunately the latter have some directory names (like include) inconsistent with the normal layout, and must be edited a little. The author warns that the method of 'system("crc ...")' is slow. I find it surprisingly fast given a decent sized cache (320K). Putting the shell and crc on a RAM disk should achieve similar benefits. It is fairly easy to change the system() to fork() + exec() so only crc needs to be reloaded every time, so a 50K cache might do. Or checkcrc could be merged with crc. 51458 2385 checkcrc.c 31800 217 listcrc #! /bin/sh # Contents: checkcrc.c listcrc # Wrapped by src@besplex on Thu Mar 8 07:43:50 1990 PATH=/bin:/usr/bin:/usr/ucb ; export PATH if test -f 'checkcrc.c' -a "${1}" != "-c" ; then echo shar: Will not clobber existing file \"'checkcrc.c'\" else echo shar: Extracting \"'checkcrc.c'\" \(2385 characters\) sed "s/^X//" >'checkcrc.c' <<'END_OF_FILE' X/* X * Check_crc.c -- Check the current file system against a CRC list X * Version 1.00 27 April 1989 X * X * Usage: X * check_crc [directory]