Path: utzoo!mnetor!tmsoft!torsqnt!jarvis.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!mit-eddie!uw-beaver!ssc-vax!bcsaic!paula From: paula@bcsaic.UUCP (Paul Allen) Newsgroups: comp.os.minix Subject: Re: CRC comparisons Message-ID: <21216@bcsaic.UUCP> Date: 5 Mar 90 21:05:48 GMT References: <8168@sdcc6.ucsd.edu> <18091@rpp386.cactus.org> Reply-To: paula@bcsaic.UUCP (Paul Allen) Organization: Boeing Computer Services AI Center, Seattle Lines: 36 In article <18091@rpp386.cactus.org> aubrey@rpp386.UUCP (Aubrey McIntosh) writes: >I wrote a simple shell script to read the various .crc >files, extract the file names, and echo the crc of the current file, >along with the correct value from the crc file, to an audit file. > >All the shelling, calling basename, crc, etc, makes it pretty slow. > >What do other people do to compare them. Surely we're not all typing >a dozen commands per file... I imagine there are lots of solutions to this one out there. Here's what I do: I run a modified version of a script someone posted some time ago. It runs in the root directory of the minix sources hierarchy (i.e. the directory that contains 'src' and 'include'). It expects a crc list on stdin that has relative pathnames from the current directory. Since the crc's that Andy sends out generally have absolute paths that are specific to his Sun, there's always some hand-editing that needs to be done for each new release. Now, 1.5.3 has the crc's in the individual directories, so I just cat'ed them all together and editted the paths. This way, once I've got the crc list squared away, I can check the entire tree with one command. It would be nice if Andy would generate the crc listings to be compatible with my script, but I suppose he's got a good reason for doing it the way he does. The output of my script is a list of the files that either don't match or don't exist. I used to have a script that went through the tree looking for files that weren't in the crc list, but I can't find it now. :-) Paul Allen -- ------------------------------------------------------------------------ Paul L. Allen | pallen@atc.boeing.com Boeing Advanced Technology Center | ...!uw-beaver!bcsaic!pallen