From owner-freebsd-hubs@FreeBSD.ORG Thu Jun 26 05:47:09 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 0E3AA37B401 for ; Thu, 26 Jun 2003 05:47:07 -0700 (PDT) Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU [128.205.32.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA3B743FE1 for ; Thu, 26 Jun 2003 05:47:06 -0700 (PDT) (envelope-from kensmith@cse.Buffalo.EDU) Received: from electra.cse.Buffalo.EDU (kensmith@localhost [127.0.0.1]) h5QCl6br004637 for ; Thu, 26 Jun 2003 08:47:06 -0400 (EDT) Received: (from kensmith@localhost) by electra.cse.Buffalo.EDU (8.12.9/8.12.9/Submit) id h5QCl50N004636 for freebsd-hubs@freebsd.org; Thu, 26 Jun 2003 08:47:05 -0400 (EDT) Date: Thu, 26 Jun 2003 08:47:05 -0400 From: Ken Smith To: freebsd-hubs@freebsd.org Message-ID: <20030626124705.GA4506@electra.cse.Buffalo.EDU> References: <3EF9A5FD.22140.3F8EC95E@localhost> <3EF9F650.2909.40C896BC@localhost> <20030625233455.GA22339@electra.cse.Buffalo.EDU> <20030625234433.GB22339@electra.cse.Buffalo.EDU> <20030626010219.GE68238@isnic.is> <20030626013823.GA24444@electra.cse.Buffalo.EDU> <20030626111127.GB10018@atrbg11.informatik.tu-muenchen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030626111127.GB10018@atrbg11.informatik.tu-muenchen.de> User-Agent: Mutt/1.4.1i Subject: Re: DNS Stuff Proposal 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: Thu, 26 Jun 2003 12:47:09 -0000 That was great! :-) I especially like the solution of creating hostmaster..freebsd.org and pointing it to the central admins if the .freebsd.org isn't strong enough to handle DNS on their own. It's not quite as simple as "send to hostmaster@freebsd.org no matter what you want" but it's definitely the next best thing and it eliminates the variability. Just one question so far. In your examples is Chris viewed as the coordinator of the FTP mirror sites, or is he the coordinator of DNS, or is he coordinator of everything (dns, ftp, cvsup, and www)? I sort of figured there would be four different people coordinating those four different things but I was guessing that was needed, I wasn't sure if one person could do all of them. And I figured they needed to be coordinated on a global basis (even if they're managed at a regional level, if that makes any sense...) if things like a sane tiering system for FTP sites is to be done, or Murray's stats collection, etc. I figured the cvsup and www services would have similar-but-different issues they face, they'd have their own equivalent of hubs@, and they'd coordinate themselves separate from the ftp sites. -- Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel |