Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-lcc!ames!ucbcad!ucbvax!decvax!tektronix!tekcrl!tekgvs!keithe
From: keithe@tekgvs.UUCP (Keith Ericson)
Newsgroups: comp.sys.amiga
Subject: Re: ... (and uuencode mess-ups)
Message-ID: <1997@tekgvs.UUCP>
Date: Thu, 8-Jan-87 12:01:08 EST
Article-I.D.: tekgvs.1997
Posted: Thu Jan  8 12:01:08 1987
Date-Received: Fri, 9-Jan-87 22:44:40 EST
References: <2280@well.UUCP> <340@oliveb.UUCP> <1213@cbmvax.cbmvax.cbm.UUCP> <2431@sdcsvax.UCSD.EDU>
Reply-To: keithe@tekgvs.UUCP (Keith Ericson)
Organization: Tektronix, Inc., Beaverton, OR.
Lines: 21

In article <2431@sdcsvax.UCSD.EDU> hutch@sdcsvax.UCSD.EDU (Jim Hutchison) writes:
>fig()
>
>Since uuen/decode do not do checksums, how about something as simple as
>using a shar with wc built into it.  That way the check travels with the
>data.  Admittedly not as good as a CRC, which I can send out source for a
>simple program that does stdin to stdout and makes sure that the CRC equals
>argv[1] (spews on stderr if a match does not occur).  Better than wc, but
>not as automatic.

How 'bout using sum(1) (from the man page):

     Sum calculates and prints a 16-bit checksum for the named
     file, and also prints the number of blocks in the file.  It
     is typically used to look for bad spots, or to validate a
     file communicated over some transmission line.

so run your file thru sum and include the value it returns with the
file, eh?

keith