Date: Mon, 5 Aug 1996 17:06:50 -0700 (MST) From: Don Yuniskis <dgy@rtd.com> To: fqueries@jraynard.demon.co.uk (James Raynard) Cc: dgy@rtd.com, questions@freebsd.org Subject: Re: perhaps i am just stupid. Message-ID: <199608060006.RAA12303@seagull.rtd.com> In-Reply-To: <199608051842.SAA02315@jraynard.demon.co.uk> from "James Raynard" at Aug 5, 96 06:42:27 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > > bin/cat > > > bin/chmod > > > /stand/cpio: invalid header: checksum error > > > DEBUG: request for bin/bin.ab from dos > > > > > > gunzip: stdin: invalid compressed data--format violated > > > DEBUG: switching back to VTY1 > > > /stand/spio: premature end of file > > > > Hmmm... seems like this pops up quite often in recent complaints. > > Indeed. > > > Is there a nice "easy" way for folks to verify checksums, etc. > > of their files before installing? Can this be added to the FAQ > > cat bin.* | gzip -t - is nice and easy, but requires a fully > functioning Unix box... I was thinking of just 'cksum bin.*' since I would *assume* that the cksums, once correct, would indicate a "good" file... > Although I believe both these utilities have been ported to DOS. > Perhaps someone with the time and inclination could knock up a > batch file to do this? gzip.exe is already on the CDROM and I > don't see any reason why cat.exe couldn't be added. how about: cksum *.* > fudge comp fudge goodsums.lst but, of course, that would require the user to have *all* the files listed in "goodsums.lst" online. Also, you'd have to create an entry for goodsums.lst in the goodsums.lst file itself! And, since DOS will create fudge before completely expanding the *.* in the cksum command, you need to take it into consideration, also.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199608060006.RAA12303>