From owner-freebsd-current Thu Mar 21 15:13:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA23421 for current-outgoing; Thu, 21 Mar 1996 15:13:58 -0800 (PST) Received: from mail.think.com (Mail1.Think.COM [131.239.33.245]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA23406 for ; Thu, 21 Mar 1996 15:13:51 -0800 (PST) Received: from Early-Bird-1.Think.COM by mail.think.com; Thu, 21 Mar 96 18:13:41 -0500 Received: from compound (fergus-26.dialup.cfa.org) by Early-Bird.Think.COM; Thu, 21 Mar 96 18:13:38 EST Received: (from alk@localhost) by compound (8.6.12/8.6.112) id RAA01294; Thu, 21 Mar 1996 17:14:41 -0600 Date: Thu, 21 Mar 1996 17:14:41 -0600 Message-Id: <199603212314.RAA01294@compound> From: Tony Kimball To: dima@FreeBSD.ORG Cc: current@freefall.freebsd.org In-Reply-To: <199603212255.OAA22228@freefall.freebsd.org> (dima@FreeBSD.ORG) Subject: Re: new sup server Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Probably you have to upgrade sup client? (to 9.x) Indeed, so I have inferred, pending verification. Perhaps I should also make explicit a further inference and an observation: Under this hypothesis, there will be a lot of folks doing this since the sup servers break against the release client. Therefore, the mirrors are not doing the trick of offloading for any but present -current users. Moreover, it is considered standard practice (for good reason) to change the port when changing protocols.