From owner-freebsd-stable@FreeBSD.ORG Thu Jun 5 22:18:51 2008 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 815F9106567C for ; Thu, 5 Jun 2008 22:18:51 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [91.103.162.4]) by mx1.freebsd.org (Postfix) with ESMTP id 3B7458FC17 for ; Thu, 5 Jun 2008 22:18:51 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from localhost (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id F025C19E027; Fri, 6 Jun 2008 00:18:49 +0200 (CEST) Received: from [192.168.1.2] (r5bb235.net.upc.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 9416619E023; Fri, 6 Jun 2008 00:18:47 +0200 (CEST) Message-ID: <48486659.6040007@quip.cz> Date: Fri, 06 Jun 2008 00:19:05 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: cz, cs, en, en-us MIME-Version: 1.0 To: Paul Schmehl References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <200806051023.56065.jhb@freebsd.org> <200806051910.20319.pieter@degoeje.nl> <3E1DBCBBB1C614B1DBD0F166@utd65257.utdallas.edu> In-Reply-To: <3E1DBCBBB1C614B1DBD0F166@utd65257.utdallas.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 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: Thu, 05 Jun 2008 22:18:51 -0000 Paul Schmehl wrote: > --On Thursday, June 05, 2008 19:10:19 +0200 Pieter de Goeje > wrote: > >> >> There's a really easy way to test this. Build & install a new kernel, but >> keep the old kernel around (by default it's in /boot/kernel.old). If the >> problem is gone, do the upgrade as usual. If it's still there, you know >> upgrading won't fix it and you don't waste time; simply rename >> kernel.old to >> kernel. This even works with 7.0 provided that you leave >> COMPAT_FREEBSD6 in >> the kernel configuration file. > > > It's not quite that simple. To do that, I have to block out time to > drive 45 miles during my supposed "off" hours and do the upgrade there. > Because, if it breaks networking and I'm at home, the server will be > down for at least an hour until I can drive to the hosting company, get > access to the server and restore the old kernel. > > Again, I'm not complaining. Just sayin' that sometimes stuff ain't > quite as easy to do as folks who are surrounded by hardware and test > platforms assume it is. I fully understand your situation, but I think there is still way to try... You can use `nextboot` command. If you install new kernel in to /boot/kernel.new/ directory, just use: nextboot -k kernel.new and then reboot the server. New kernel will be used for this (and only this) cycle. So if something goes wrong and you have any possibility to reboot server again (PDU or by phone call to collocation), you will be back with old good kernel without need to travel. I did it a few times and it saved me ;) Miroslav Lachman