Date: Wed, 14 Aug 2002 10:26:59 -0400 From: Michael Lucas <mwlucas@blackhelicopters.org> To: Barney Wolff <barney@tp.databus.com> Cc: Matthias Trevarthan <trevarthan@wingnet.net>, freebsd-stable@FreeBSD.ORG Subject: Re: setting up a CVSup repository Message-ID: <20020814102659.A87482@blackhelicopters.org> In-Reply-To: <20020814140526.GA29078@tp.databus.com>; from barney@tp.databus.com on Wed, Aug 14, 2002 at 10:05:26AM -0400 References: <200208140919.35737.trevarthan@wingnet.net> <20020814140526.GA29078@tp.databus.com>
next in thread | previous in thread | raw e-mail | index | archive | help
If all of your servers are identical, you can certainly do the NFS mount method described below. That's absolutely preferable for *most* people. If you need different make options on the various machines, though, that's not that useful. You can build multiple worlds with different make options, but that may be more trouble than building locally. In some environments, you cannot use NFS mounts across the firewalls between application tiers. A central cvsup server is quite useful there. Also, if you're in an enterprise setting, each version of the code must separately pass QA. If you cvsup each server separately, this is bad. (I've been in a situation before where one server crashed, while all the others didn't. The problem turned out to be slight differences in the version of -stable I was running at the time. Tracking that down was utter hell. That's my motivation for using a central cvsup server. :-) ==ml On Wed, Aug 14, 2002 at 10:05:26AM -0400, 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: > > 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 simpler > 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. > > 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 actually do #2 but only do the checkout on the local machine and > build there. > > On Wed, Aug 14, 2002 at 09:19:35AM -0400, Matthias Trevarthan wrote: > > I'd like to set up a repository on ONE server for all the ports AND /usr/src. > > > > Then I'd like my other machines to download it via cvsup just like they would > > from some machine out on the net, but with the speed of 10/100... > > -- > Barney Wolff > I'm available by contract or FT: http://www.databus.com/bwresume.pdf > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org http://www.oreillynet.com/pub/q/Big_Scary_Daemons Absolute BSD: http://www.AbsoluteBSD.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020814102659.A87482>