From owner-freebsd-isp@FreeBSD.ORG Tue Dec 20 00:28:30 2005 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E1A116A41F for ; Tue, 20 Dec 2005 00:28:30 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from wjv.com (fl-65-40-24-38.sta.sprint-hsd.net [65.40.24.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28B5D43D88 for ; Tue, 20 Dec 2005 00:28:23 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by wjv.com (8.13.5/8.13.1) with ESMTP id jBK0SLVY016101 for ; Mon, 19 Dec 2005 19:28:21 -0500 (EST) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.13.5/8.13.1/Submit) id jBK0SFd5016100 for freebsd-isp@freebsd.org; Mon, 19 Dec 2005 19:28:16 -0500 (EST) (envelope-from bv) Date: Mon, 19 Dec 2005 19:28:15 -0500 From: Bill Vermillion To: freebsd-isp@freebsd.org Message-ID: <20051220002815.GB15974@wjv.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on bilver.wjv.com Subject: Re: upgrades X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bv@wjv.com List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Dec 2005 00:28:30 -0000 They all laughed on Mon, Dec 19, 2005 at 17:24 when mike@lanline.com said: > > One of the things that seems to be very vague to me is the FreeBSD > upgrade procedure. I see that I can do a binary upgrade off the cd's, but > I'm more curious about the source upgrade procedure. Does it do a > through job (i.e. does it remove older non-existent binaries when > upgrading)? Or should I only upgrade like that once or twice and do a > fresh install after like the 3rd time? Also, is it a good idea to have > one server that has CVSup running on the src and ports dir and then have > all the other servers nfs mount those directories and do all the upgrades > off of the one machines src and port dirs? If there are new binaries the same as the old ones, they are over-written. There aren't that many that are left when upgrades are done - but you can check by doing a reverse listing in the key directories /bin /sbin /etc. Since I maintain servers in a colo I've upgraded some all the way from 4.1 to/thru the 4.11 - all remotely - with never doing a fresh install. Before you do that test all your machines to make sure they will reliably boot remotely even if someone unplugs the keyboards or moves the KVMs around. As to having one CVSsup on one machine and using nfs for the others that is up to you. I don't run nfs on any of the machines, and run cvs on each server nightly. [I have 100Mbs links into a 40Gb backbone so there's no bandwidth problems]. Where you can run into stale binaries are things from ports where things change - and if you forget to perform portupgrade and just do a new install. Sometimes locations change. I'm still running 4.x on all the servers, and will probably move to the 6 series when 6.1 comes out and is stable. Since these are all production machines I tend to be overcautious. Bill -- Bill Vermillion - bv @ wjv . com