Interesting; I can't seem to fetch boot-unstr2.fs from
NetBSD-1.4/i386/installation/floppies on the FTP site.  Has anybody
else run into this?  It stops about 300 bytes from the end of the
file.  My hunch would be that, somewhere between there and here (here
== avicom.net, via Cable & Wireless), there's a router that's puking
on a particular byte pattern.  I can grab the .gz version of the file
without any trouble.

Not having run into one of these before, does anybody have any advice
on figuring out where the problem lies?

Chris

$ traceroute ftp.netbsd.org
 1  pm1 (208.128.130.248)  1953.727 ms  1956.439 ms  1600.022 ms
 2  gateway (208.128.130.254)  1735.283 ms  1599.357 ms  1505.436 ms
 3  border8-serial2-2.Denver.cw.net (204.70.156.17)  1505.365 ms  1728.261 ms  1736.616 ms
 4  core2-fddi-1.Denver.cw.net (204.70.152.65)  1504.068 ms  1598.162 ms  1601.251 ms
 5  core4.WillowSprings.cw.net (204.70.4.73)  1762.944 ms  1917.461 ms  1843.096 ms
 6  aads.above.net (198.32.130.71)  1640.652 ms  1754.512 ms  1728.802 ms
 7  chicago-core1.ord.above.net (209.249.0.129)  1674.791 ms  328.190 ms  279.662 ms
 8  sjc-chicago-oc3.above.net (209.249.0.125)  194.150 ms  238.357 ms  191.527 ms
 9  pao-sjc-oc12.pao.above.net (209.133.31.150)  485.828 ms  210.817 ms  190.334 ms
10  mibh-above-oc3.pao.mibh.net (216.200.0.10)  224.398 ms  210.814 ms  191.637 ms
11  pa1a.feed1.pla.mibh.net (204.152.184.195)  226.999 ms  265.854 ms  257.344 ms
12  ifw2-core.pa.vix.com (204.152.184.5)  204.657 ms  210.662 ms  216.529 ms
13  ftp.netbsd.org (204.152.184.75)  191.575 ms  201.412 ms  303.158 ms

-- 
-----------------------------------------------------cjones@avicom.net
Chris Jones                                          cjones@honors.montana.edu
           Mad scientist at large
"Is this going to be a stand-up programming session, sir, or another bug hunt?"