From owner-freebsd-isp@FreeBSD.ORG Wed Apr 26 16:15:24 2006 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 D4CE016A544 for ; Wed, 26 Apr 2006 16:15:24 +0000 (UTC) (envelope-from cody@wilkshire.net) Received: from mail.wilkshire.net (mail.wilkshire.net [12.111.120.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2659C43D48 for ; Wed, 26 Apr 2006 16:15:23 +0000 (GMT) (envelope-from cody@wilkshire.net) Received: (qmail 32116 invoked from network); 26 Apr 2006 12:15:22 -0400 Received: from unknown (HELO localhost) (10.10.55.23) by 10.10.55.20 with SMTP; 26 Apr 2006 12:15:22 -0400 Received: from mail.wilkshire.net ([10.10.55.20]) by localhost (virusproxy3.wilkshire.net [10.10.55.23]) (amavisd-new, port 10024) with ESMTP id 20340-17; Wed, 26 Apr 2006 12:15:14 -0400 (EDT) Received: from [10.57.128.241] (unknown [12.111.120.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.wilkshire.net (Postfix) with ESMTP id A681CA74270; Wed, 26 Apr 2006 12:15:14 -0400 (EDT) Message-ID: <444F9C91.9010205@wilkshire.net> Date: Wed, 26 Apr 2006 12:15:13 -0400 From: Cody Baker User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: freebsd-isp@freebsd.org References: <20060426104803.GO4202@over-yonder.net> <20060426134530.GB8912@uk.tiscali.com> <20060426150732.GQ4202@over-yonder.net> In-Reply-To: <20060426150732.GQ4202@over-yonder.net> X-Enigmail-Version: 0.94.0.0 X-Virus-Scanned: amavisd-new at wilkshire.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Router upgrade.... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Apr 2006 16:15:24 -0000 I don't have a lot of 6.0 experience but I'm going to really recommend that for a production server that you let this chill a little bit before installing a release candidate. In my younger days I got burned pretty hard by installing RC freebsd. Thank You, Cody Baker cody@wilkshire.net Matthew D. Fuller wrote: > On Wed, Apr 26, 2006 at 02:45:30PM +0100 I heard the voice of > Brian Candler, and lo! it spake thus: > >> I think you're forgetting the time sat in single-user mode while >> doing installworld and manually mergemaster'ing the rc scripts. >> > > No, I'm not, because I wouldn't do that :) > > When I upgraded some production systems from RELENG_2_2 to mid-life > RELENG_4, you're darn tootin' I did a lot of work in single-user mode > (and some off boot disks, for that matter). But extraordinary > circumstances aside, I do virtually all my upgrades in normal > multi-user, and often many miles from the console. > > Now, I get away with it because I've done a lot of upgrades before, > and I watch the mailing lists and keep track of any gotchas in a given > upgrade. But Usually(tm) there's not even a twitch. I've done > upgrades from 5.3/5.4ish to RELENG_6 remotely (no console, just ssh) > several times, on i386 and amd64, and wouldn't flinch at doing it > again. > > To a large extent, the smoothness of doing so is related to how often > you do it; if you go a year or two between upgrades, accumulated > differences can make things really unpleasant, while doing it every > few months is usually grass through a duck. > > > >> Personally I prefer the other option suggested by the OP: >> - build a brand new router using whatever O/S and software revisions you >> choose to be on >> > > Which is the other extreme. I've rarely been in a situation where I > consider my "normal" method too risky and went with something like > this, but "rarely" isn't "never". > > In the end, you always have to balance. In the OP's case, I wouldn't > be too worried about just doing it in-place; whether that would apply > for anyone else, I (obviously) couldn't say. > > > >> If you want it to come up on the same IP address then you may have >> to clear ARP caches on some other devices on the same LAN >> segment(s), but that's about it. >> > > If you got real smart, you could just pull the NIC and put it in the > new box, so even if something was foolishly holding onto the MAC, it > would still get there :) > > >