>Date: Wed, 13 Dec 1995 00:20:43 -0600
   >From: Chris Csanady <ccsanady@friley14.res.iastate.edu>
   
   >SUP 8.26 (4.3 BSD) for file /etc/supfile.netbsd at Dec 12 23:04:14
   >SUP: Read error on network: Connection reset by peer
   >SUP: Network write timed out
   >SUP Upgrade of current-allsrc at Tue Dec 12 23:15:20 1995
   >SUP: Error reading file list from file server
   >SUP: Upgrade of current-allsrc aborted at Dec 12 23:15:20 1995
   >SUP: Network write timed out
   
   This looks like network troubles, although it could also be something
   as simple as an incorrect hostbase.

i would say the same, but, i've been having the exact same problem
recently, repeatedly:

SUP Updating file src/distrib/notes/sun3/upgrade
SUP Updating file src/distrib/notes/sun3/whatis
SUP Updating file src/distrib/notes/sun3/xfer
SUP: Read error on network: Connection reset by peer
SUP: Premature EOF on network input
SUP: Network write timed out
SUP: Error receiving file from file server
SUP: Upgrade of current-src aborted at Dec 14 00:45:50 1995
SUP: Network write timed out
SUP: Aborted

is the latest one.  my sup file says:

current release=src host=sup.netbsd.org. hostbase=/a/anon_ftp base=/usr prefix=/orb/q/src use-rel-suffix delete compress

(hasn't changed for a *long* time).


i don't think it's a network problem cuz i was able to maintain a
shell to said host the entire time (with the frequent return to
ensure that the connection was alive).

anyone?