Subject: Re: sup problems for current-domestic?
To: Michael Graff <explorer@flame.org>
From: Rob Healey <rhealey@altair.helios.mn.org>
List: current-users
Date: 12/25/1995 11:51:11
> >SUP Receiving file src/domestic/usr.sbin/kdb_init/kdb_init.c
> >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-security aborted at Dec 24 10:29:39 1995
> >SUP: Network write timed out
> >SUP: Aborted
> 
> I have thought there must be a bug in sup for some time now.  If you
> are not using compression, enable that and it might work.  I had to do
> that to even get past allsrc...
> 
	They might be in the same boat I am. No matter what I tried,
	-o, -k, -z and a zillion other combinations, sup would NOT
	work for me on either amiga or sparc, 28.8 modem or 10Mbit
	right off the backbone.

	I finally had to FTP the tarballs to create the initial tree. The
	minor sup changes from day to day seem to transfer OK but I'll
	bet if alot of changes happen at once I'll have to refetch the
	tarballs.

	I got network resets and file receive -1 errors.

		-Rob