From owner-freebsd-hubs@FreeBSD.ORG Tue Jun 10 11:48:16 2003 Return-Path: Delivered-To: freebsd-hubs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC2D837B401 for ; Tue, 10 Jun 2003 11:48:16 -0700 (PDT) Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id C397043FAF for ; Tue, 10 Jun 2003 11:48:15 -0700 (PDT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (wxklmr@localhost [127.0.0.1]) by lurza.secnetix.de (8.12.8p1/8.12.8) with ESMTP id h5AImAB5006034; Tue, 10 Jun 2003 20:48:10 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.12.8p1/8.12.8/Submit) id h5AImAVt006033; Tue, 10 Jun 2003 20:48:10 +0200 (CEST) From: Oliver Fromme Message-Id: <200306101848.h5AImAVt006033@lurza.secnetix.de> To: kensmith@cse.Buffalo.EDU (Ken Smith) Date: Tue, 10 Jun 2003 20:48:09 +0200 (CEST) In-Reply-To: <20030610164328.GD2099@electra.cse.Buffalo.EDU> from "Ken Smith" at Jun 10, 2003 12:43:28 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit cc: freebsd-hubs@freebsd.org Subject: Re: [FreeBSD-Announce] FreeBSD 5.1 Released! X-BeenThere: freebsd-hubs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD Distributions Hubs: mail sup ftp List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2003 18:48:17 -0000 Ken Smith wrote: > On Tue, Jun 10, 2003 at 06:24:06PM +0200, Oliver Fromme wrote: > > On the other hand -- When someone from the RE team posts > > a message to hubs@ like "5.1 for i386 available now!", > > I guess many people will start their sync jobs immediately. > > That's already some kind of "push". So there's the same > > load situation, except everyone has started the thing > > manually, instead of having it initiated automatically. > > Yup. But that's arguably a "special case". If you can fold the special > case into what you use for day-to-day stuff that's great. But sometimes > it's best to design the system for the day-to-day stuff and leave the > special cases as special cases. Depends on how often the special cases > come along. That's exactly what I meant when I mentioned those two cases. The day-to-day stuff (i.e. syncing distfiles etc.) doesn't have to change at all. Heck, those don't even have to be mirrored daily. It works perfectly well as it is now. At least as far as I'm concerned. The problem is when we're approaching a release, and the messages on hubs@ arrive almost hourly saying that these releases and those packages have been uploaded. Sometimes it is important to sync as fast as possible, because some things have only a short lifetime anyway, such as some release candidates. This is where an automated "push" or notification mechanism would be really beneficial. By the way, yesterday (the day 5.1-release went out) was a holiday in Germany ("Pfingstmontag"), and I guess in other parts of the world, too. Another reason to have an automatism for syncing, because many people probably just weren't there to do things manually. Maybe I'm wrong, though. :-) Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "The only reasonable alternative we can come up with is to close off the Internet to America Online users until they have passed an entrance test. But that would break federal laws that prohibit discrimination against the intellectually challenged." -- hhahn@boardwatch.com