Date: Fri, 02 Feb 1996 10:31:42 -0800 From: "Justin T. Gibbs" <gibbs@freefall.freebsd.org> To: "Karl Denninger, MCSNet" <karl@mcs.com> Cc: jkh@time.cdrom.com (Jordan K. Hubbard), hackers@freebsd.org Subject: Re: And the winner is! Message-ID: <199602021831.KAA10533@freefall.freebsd.org> In-Reply-To: Your message of "Fri, 02 Feb 1996 10:19:32 CST." <m0tiOCz-000IDUC@venus.mcs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> > b) How to handle replication? I know how to do this on BSDI, >> > but on FreeBSD it has always eluded me. Presume that there >> >> You want to be able to stamp out multiple machines from one build, >> or..? I'm afraid that "replication" is a little ambiguous in this >> context. Due to a number of historical bogons in our build process, I >> still recommend that each and every machine have its own copy of >> /usr/src, the problems with shared obj links otherwise becoming a real >> pain. > >No, we want to be able to have a "code server" which can load, and keep >updated, multiple machines. That is, when I have system #15 to load, I want >to plug in the Ethernet, point the new box at the server, and say "go fetch >your load, kid". > >Also, the ability to somehow have this update process automated (so that I >only have to make a code change on *ONE* machine) would be nice. This can be done with SUP. I have some sample collections from the HP-UX clusters managed by TCS at U.C. Berkeley that I will be adopting to FreeBSD soon. They'll pop up in the sup examples directory when I'm done. >I don't care about /usr/src; the production machines don't have to have the >storage, or the ability, to customize things *for themselves only*. There >are a couple of files that don't get screwed with (obviously -- they are >different, such as the stuff in /etc) but the rest should be able to be kept >current without hassling over doing it by hand. The TCS system uses a script to process all files that need to be customized for the host. When a file is pulled down via SUP, this one script is run on the file to do the customization. SUP will also do things like hup sendmail when the sendmail.cf file changes. The TCS collections are very complex, but since I wrote them, it shouldn't take too long to make them work for basic FreeBSD systems. You'll have to modify them for your setup of course. >-- >Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity >Modem: [+1 312 248-0900] | T1 from $600 monthly; speeds to DS-3 available >Voice: [+1 312 803-MCS1] | 21 Chicagoland POPs, ISDN, 28.8, much more >Fax: [+1 312 248-9865] | Email to "info@mcs.net" WWW: http://www.mcs.net >/ >ISDN - Get it here TODAY! | Home of Chicago's only FULL Clarinet feed! -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199602021831.KAA10533>