Date: Wed, 07 Aug 1996 07:36:06 -0400 From: Gary Chrysler <tcg@ime.net> To: Don Yuniskis <dgy@rtd.com> Cc: James Raynard <fqueries@jraynard.demon.co.uk>, questions@freebsd.org Subject: Re: perhaps i am just stupid. Message-ID: <32087FA6.3567@ime.net> References: <199608061917.MAA07140@seagull.rtd.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Don Yuniskis wrote: > > > > > 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). > Hmmm, I wasn't thinking of on_the_fly installations either. > Obviously, better techniques exist. But, this seems like a > "no code" quicky that you could *read* to someone over the phone... But it's not a 'No Code' quicky.. Wheres the Dos based cksum thats compatiable with FreeBSD's cksum's output?? -Enjoy Gary ~~~~~~~~~~~~~~~~ Improve America's Knowledge... Share yours The Borg... Where minds meet (207) 929-3848
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?32087FA6.3567>