From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 19:00:35 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 38113106566B for ; Tue, 28 Dec 2010 19:00:35 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from outgoing01.lava.net (outgoing01.lava.net [IPv6:2001:1888:0:1:230:48ff:fe5b:3b50]) by mx1.freebsd.org (Postfix) with ESMTP id D48048FC21 for ; Tue, 28 Dec 2010 19:00:34 +0000 (UTC) Received: from malasada.lava.net (malasada.lava.net [64.65.64.17]) by outgoing01.lava.net (Postfix) with ESMTP id 2926014E63A; Tue, 28 Dec 2010 09:00:33 -1000 (HST) Received: by malasada.lava.net (Postfix, from userid 102) id 67148196E1C; Tue, 28 Dec 2010 09:00:33 -1000 (HST) Date: Tue, 28 Dec 2010 09:00:33 -1000 From: Clifton Royston To: Jason Helfman Message-ID: <20101228190032.GA3031@lava.net> Mail-Followup-To: Jason Helfman , freebsd-stable@freebsd.org References: <20101227224426.GA11955@lava.net> <20101227224752.GC1505@eggman.experts-exchange.com> <20101227225828.GB11955@lava.net> <4D1931FA.3070403@my.gd> <4D1934B3.8080102@FreeBSD.org> <20101228062028.GA95888@eggman.experts-exchange.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101228062028.GA95888@eggman.experts-exchange.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: Accidentally aborted upgrade via freebsd-update - how to recover? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2010 19:00:35 -0000 On Mon, Dec 27, 2010 at 10:20:28PM -0800, Jason Helfman wrote: > On Mon, Dec 27, 2010 at 04:52:03PM -0800, Doug Barton thus spake: > >On 12/27/2010 16:40, Damien Fleuriot wrote: > >>On 12/27/10 11:58 PM, Clifton Royston wrote: > >>> OK, and oh well... I wish there were some way to automate the diffing > >>>out of the $FreeBSD lines. I suppose those might be the artifact of > >>>some previous upgrade, so that the file version present is not the one > >>>expected for FreeBSD 6.1. > >> > >>Wait, do you mean like, mergemaster -F ? > >> > >>Excerpt from the manual: > >> -F If the files differ only by VCS Id ($FreeBSD) install > >>the new file. > >> > >> > >>I've discovered this rather recently, it's a *lifesaver* > >> > >>This comes from fbsd7's version though, I can not say for the one you're > >>still running on fbsd6 > > > >You always want to run mergemaster from the version you are upgrading > >_to_. It doesn't happen often (by design) but occasionally mergemaster > >has to grow "special knowledge" of specific files/directories/etc. in a > >new FreeBSD version. > > As far as I can tell, freebsd-update doesn't use mergemaster. > > /usr/src/usr.sbin/freebsd-update/freebsd-update.sh > > Source installation does, however I don't believe a binary upgrade does. It might be an interesting project to work on enhancing freebsd-update to use mergemaster - shared code, DRY, and all that. ... A brief update for the curious: this turned into the "sharks circling" kind of upgrade though not through any fault of freebsd-update. It turned out after I had done the initial install steps at the console that 7.1 doesn't detect the built-in re0 GbE interface on this motherboard, which threw a major monkeywrench in the way of rebuilding all the ports. I should have recalled that there were some ongoing re problems which Pyun was fixing around the time of 7.1. As I didn't want to downgrade - and couldn't safely after having installed userland prematurely - I had a backup plan of booting from the CD drive, which then turned out to have failed mechanically. Fortunately this is my home server and isn't running anything critical. I stole a CD drive from my usual desktop computer and could boot the loader/kernel on a 7.3 CD, which detects everything. Following that, rebooting via the hard drive got the interface running again. (Why, I don't know - I suspect it might be somehow picking up either the 7.3 loader or hints due to having the CD set as the BIOS boot drive.) I got the old ports removed and essential ports rebuilt with portsnap and portmaster (thank you, Doug Barton) and I'm pressing ahead with an upgrade to 7.3 since it appears that kernel will work fine with this motherboard. -- Clifton -- Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services