From owner-freebsd-questions Tue Aug 6 12:17:09 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA12781 for questions-outgoing; Tue, 6 Aug 1996 12:17:09 -0700 (PDT) Received: from seagull.rtd.com (root@seagull.rtd.com [198.102.68.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA12771 for ; Tue, 6 Aug 1996 12:17:06 -0700 (PDT) Received: (from dgy@localhost) by seagull.rtd.com (8.7.5/8.7.3) id MAA07140; Tue, 6 Aug 1996 12:17:01 -0700 (MST) From: Don Yuniskis Message-Id: <199608061917.MAA07140@seagull.rtd.com> Subject: Re: perhaps i am just stupid. To: fqueries@jraynard.demon.co.uk (James Raynard) Date: Tue, 6 Aug 1996 12:17:01 -0700 (MST) Cc: dgy@rtd.com, questions@freebsd.org In-Reply-To: <199608061030.KAA01620@jraynard.demon.co.uk> from "James Raynard" at Aug 6, 96 10:30:38 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > 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... [snip] > I can see problems fitting this into the download-and-extract-on-the-fly > scheme of things. For instance, if you're downloading over a modem, > and bin.aa is corrupted, would you really want to have to wait until > everything up to bin.cx has come down before finding it out? > (Especially if it's some sort of systematic error and every file > you've spent the last two hours downloading is corrupt...) Ah, I wasn't advocating putting it into the "automated" path. Rather, consider someone who has *manually* ftp'ed stuff onto their DOS box and then started to unpack it all. This would give them a tool to test the integrity of each file before gzip chokes on it (which some of the recent posts seem to be griping about). > > > 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 > > Or have a separate checksum file for each dist. Yes, in a separate post, I suggested: cksum %1.0* > %1.tmp comp %1.tmp %1.lst For those who are truly lazy, you could wrap this batch file in yet another: chkzips bin chkzips sbin chkzips sec ... > > 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. > > Or put fudge and goodsums.lst in a different directory? Or give them names that don't conflict with any of the distributions! :> Obviously, better techniques exist. But, this seems like a "no code" quicky that you could *read* to someone over the phone... --don