From owner-freebsd-stable Fri Nov 17 21: 3: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from shell.webmaster.com (unknown [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 6E73837B479 for ; Fri, 17 Nov 2000 21:02:58 -0800 (PST) Received: from whenever ([216.152.68.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Fri, 17 Nov 2000 21:02:09 -0800 From: "David Schwartz" To: Cc: Subject: RE: New US CVSup mirrors Date: Fri, 17 Nov 2000 21:02:57 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal In-Reply-To: <200011180452.eAI4qdQ61639@vashon.polstra.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I suppose it would be OK if it were elective and not required. It > has a lot of potential problems. First, different mirrors sync to > the master server at different times. If you update twice in rapid > succession from different servers, the second update might actually > back you up to an earlier version than the first one. Even worse, if > something went wrong at one of the mirrors in the rotation such that > it was far out of date, it could revert your sources by a lot. > > John > -- > John Polstra These problems could be solved if: 1) People who used the random server understood that they couldn't 'cvsup' more than once in rapid succession. 2) The list of available servers were reasonably well maintained so that busy or stale servers were removed from it in a timely manner. One big disadvantage, however, would be that people could't pick a 'cvsup' server that was very close to them. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message