From owner-freebsd-stable Wed Jan 10 14:13:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from staff.nyi.net (staff.nyi.net [204.248.157.16]) by hub.freebsd.org (Postfix) with SMTP id 181EE37B6A0 for ; Wed, 10 Jan 2001 14:12:50 -0800 (PST) Received: (qmail 15713 invoked by uid 1004); 10 Jan 2001 22:08:02 -0000 Message-ID: <20010110220802.15712.qmail@staff.nyi.net> From: "Javier Frias" To: freebsd-questions@freebsd.org Cc: freebsd-stable@freebsd.org Subject: Central Source Updates Date: Wed, 10 Jan 2001 22:08:02 GMT Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm wondering what everyone here is doing to do centralized source updates on their server farms. Right now we've been doing it manually on each server, but now we are trying to come up with procedures to try to centralized the situation a bit. I've come up with two basical startegies. One central and one localized. 1) Central Having one source repository server and one compile/build server. the source repository would be just a basic freebsd mirror. The build server would be a machine that would keep different versions of FreeBSD in both source and binary form, compiled witht he optimazations to our liking ie /disk01/FreeBSD4-STABLE/00010120/src /disk01/FreeBSD4-STABLE/00010120/obj these directories woud be nfs exportable read-only. so when a machine wants to update it's system would mount thses dir's over their /usr and /usr/obj and do a make install. PROS: quick CONS: donot get to test machines, i like make world since they are usually good at detecting hardware issues ( memory disk etc ) 2) Localized Having one source repository server the source repository would be just a basic freebsd mirror. machines would use cvs to update to a specify version date combination. and build locally Packages would mostly not be an issue, since we are pushing all developers to make custom freebsd packages for all the software we use, and we'll test each on the specific OS combinations. SO, does anyone have any comments or pointers on how to better these solutions or which is better to use. any pointers to articles, documents etc? ( besides the handbook section on updating :-P ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message