From owner-freebsd-stable Fri Nov 17 21:26: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 4B9E037B479 for ; Fri, 17 Nov 2000 21:25:57 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id VAA05091; Fri, 17 Nov 2000 21:25:47 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.0/8.11.0) id eAI5Pkb61768; Fri, 17 Nov 2000 21:25:46 -0800 (PST) (envelope-from jdp) Date: Fri, 17 Nov 2000 21:25:46 -0800 (PST) Message-Id: <200011180525.eAI5Pkb61768@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Reply-To: stable@freebsd.org Cc: davids@webmaster.com Subject: Re: New US CVSup mirrors In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , David Schwartz wrote: > 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. I can tell you from direct experience that #2 is for all practical purposes impossible to achieve. First I'd have to find out about a server having problems. Then the DNS-meister would have to see my mail and do something about it. Then the updated DNS records would have to trickle into everybody's caches. Maintaining lists of constantly changing things is Just Hard. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message