From owner-freebsd-current Tue Jan 25 13:20:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id E0CBB14E8F for ; Tue, 25 Jan 2000 13:20:24 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA66915; Tue, 25 Jan 2000 13:16:20 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: charon@freethought.org Cc: Bill Swingle , current@FreeBSD.ORG Subject: Re: connectivity problems with current.freebsd.org In-reply-to: Your message of "Tue, 25 Jan 2000 12:19:09 CST." <4.2.2.20000125121223.00b36100@nsit-popmail.uchicago.edu> Date: Tue, 25 Jan 2000 13:16:20 -0800 Message-ID: <66912.948834980@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm sure this is a silly question, but then why does usw3 appear to _be_ a > mirror? Why have usw3 at all? It's NOT a mirror and I really wish people would stop jumping to conclusions with tenuous data because it's really very simple and not like anyone is currently speculating: 1. There is a machine called current.freebsd.org (AKA usw2) which runs 4.0-current and builds -current snapshots. 2. There is a machine called releng3.freebsd.org (AKA usw3) which runs 3-stable and builds -stable snapshots. 3. Both of these machines share a large ccd disk volume (I don't need vinum to do what I already have ccd working just fine on) which they copy their successful snapshots to. 4. Each machine runs an ftpd and points to this common volume for exporting the bits in a way which is obviously easier for me to maintain. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message