>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.

As a general rule, people should include a copy of their supfile in
any messages about sup problems.

>or something about failing to retreive a file in /usr/src/bin/ed/test...

I had problems with files in src/bin/ed/test, too.  Sup has problems
with 0-length files for some reason.
-- 
Mike Long <mike.long@analog.com>           http://www.shore.net/~mikel
VLSI Design Engineer         finger mikel@shore.net for PGP public key
Analog Devices, CPD Division          CCBF225E7D3F7ECB2C8F7ABB15D9BE7B
Norwood, MA 02062 USA       (eq (opinion 'ADI) (opinion 'mike)) -> nil