From owner-freebsd-stable Wed Aug 14 7:32:11 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5018037B401 for ; Wed, 14 Aug 2002 07:32:06 -0700 (PDT) Received: from agape.wingnet.net (agape.wingnet.net [206.30.215.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9793443E75 for ; Wed, 14 Aug 2002 07:32:05 -0700 (PDT) (envelope-from trevarthan@wingnet.net) Received: from david.int.wingnet.net (makrothumia.wingnet.net [206.30.215.5]) by agape.wingnet.net (8.11.6/8.11.6) with ESMTP id g7EEW5L13972 for ; Wed, 14 Aug 2002 10:32:05 -0400 (EDT) (envelope-from trevarthan@wingnet.net) Content-Type: text/plain; charset="iso-8859-1" From: Matthias Trevarthan Reply-To: trevarthan@wingnet.net Organization: Urokosodoji, Inc. To: freebsd-stable@freebsd.org Subject: Re: setting up a CVSup repository Date: Wed, 14 Aug 2002 10:32:04 -0400 User-Agent: KMail/1.4.2 References: <200208140919.35737.trevarthan@wingnet.net> <20020814140526.GA29078@tp.databus.com> In-Reply-To: <20020814140526.GA29078@tp.databus.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200208141032.04447.trevarthan@wingnet.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wednesday 14 August 2002 10:05 am, Barney Wolff wrote: > This can be done, as another poster has indicated. But it may be too > much effort for what you want to accomplish. There are multiple ways > to administer a collection of FreeBSD systems without having each one > do its own cvsup: > Nope. This is exactly what I want.=20 > 1. As you asked, set up your own cvsup mirror. It seems to me that > this is the way to go only if the systems that will be using it are > not under your direct supervision. > > 2. Do cvsup of the cvs archive on one machine, then have others do > their own remote CVS checkouts from the archive on that. This is simpl= er > in some ways on the server, and really no harder on the clients. It > allows you to build current and stable and cpu flavors, as you wish. > I'm a little confused about the differences between one and two. Could yo= u=20 elaborate?=20 > 3. cvsup on one machine, build on that, and have all the others > NFS mount /usr/src, /usr/obj and /usr/ports. This has the feature > that you control which version is in use and saves a lot of time on > all the client machines. It is clearly the way to go if all the > machines are under your supervision and you're willing to build > stuff that will run on all your cputypes - the optimizations available > for each type are really minor within the x86 family so the loss > of the last inch of performance is worth the generality, imho. I > build separate kernels for each x86 flavor but a common world. > I'm not real fond of NFS. We have a somewhat distributed network, with=20 multiple server rooms connected by T1s. They're all under my administrati= on,=20 but I think running CVSup on each machine is fairly ideal. UNIX machines=20 multitask pretty well, and it only takes about two hours to make buildwor= ld=20 on my beefy servers.=20 I may do this within server rooms though.. Have one master server downloa= d and=20 build the world in each room, then distribute via NFS inside each room...= =20 Don't know. I'll have to think about it. > I actually do #2 but only do the checkout on the local machine and > build there. Again, how does this differ from #1? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message