Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ukma!uflorida!haven!decuac!grebyn!escom!al
From: al@escom.com (Al Donaldson)
Newsgroups: comp.os.minix
Subject: Re: CRC comparisons
Message-ID: <527@escom.com>
Date: 7 Mar 90 18:56:00 GMT
References: <8168@sdcc6.ucsd.edu> <18091@rpp386.cactus.org> <21216@bcsaic.UUCP>
Organization: ESCOM Corp., Oakton, VA
Lines: 29

In article <21216@bcsaic.UUCP>, paula@bcsaic.UUCP (Paul Allen) writes:
> In article <18091@rpp386.cactus.org> aubrey@rpp386.UUCP (Aubrey McIntosh) writes:
> >What do other people do to compare them.  Surely we're not all typing
> >a dozen commands per file...

> 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.  

As part of the unshar'ing, patching, and checking process, I run Andy's 
*.crc file through sed to pull out the absolute path, and then I save it 
in a file CRC.155 (for example) to indicate the release number:

	cat *.crc | sed 's:/home.*/::' > CRC.155
	crc * > CRC
	diff CRC CRC.155

I find that associating the name of the CRC file with the release version
is a handy way for me to keep track of what release I'm working with 
(for example, 153 FS and MM with 152 kernel..), and especially so if I
have multiple versions of MINIX on my machine.

The above is part of a csh-script I wrote on my Sun to do the unshar'ing,
patching, and checking for one directory.  I didn't post the whole script
because it's for csh, it's ugly, it's damn ugly, and it doesn't handle 
unexpected conditions very well.  But the fragment above handles the
CRC checking very nicely -- wish I'd thought of it back at 1.4.n.  :-)

Al