From owner-freebsd-current  Thu Mar 21 14:55:51 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA22235
          for current-outgoing; Thu, 21 Mar 1996 14:55:51 -0800 (PST)
Received: (from dima@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA22228
          Thu, 21 Mar 1996 14:55:49 -0800 (PST)
Message-Id: <199603212255.OAA22228@freefall.freebsd.org>
Subject: Re: new sup server
To: alk@Think.COM (Tony Kimball)
Date: Thu, 21 Mar 1996 14:55:49 -0800 (PST)
Cc: current@freefall.freebsd.org
In-Reply-To: <199603212210.QAA00889@compound> from "Tony Kimball" at Mar 21, 96 04:10:14 pm
From: dima@FreeBSD.ORG (Dima Ruban)
X-Class: Fast
Organization: HackerDome
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Tony Kimball writes:
> 
> 
>    From: Paul Traina <pst@shockwave.com>
>    Date: Thu, 21 Mar 1996 11:54:05 -0800
>    Subject: Re: new sup server 
> 
>    I would suggest that we coordinate as follows, to avoid overloading the T1
>    to freefall:
> 
> This won't do as much good as it should, unless the mirrors work for
> those as point at them.  I mentioned this on -questions, but perhaps
> it bears repeating, that *only* freefall is working for me
> using the 2.1R client.  I suspect the mirrors are running newer
> versions of the server (although I have not investigated at length).
> 
> sup -v sup5.current
> SUP 8.26 (4.3 BSD) for file sup5.current at Mar 21 15:32:28

Probably you have to upgrade sup client? (to 9.x)

> SUP: Read error on network: Connection reset by peer
> SUP: Network write timed out
> SUP Upgrade of src-base-current at Thu Mar 21 15:44:31 1996
> SUP: Error reading signon reply from fileserver
> 
> Similarly sup2, sup3, while sup4 refuses connections with perfect
> consistency to date.
> 

-- dima