From owner-freebsd-current@FreeBSD.ORG Mon Mar 1 18:53:19 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF7DC16A4CE for ; Mon, 1 Mar 2004 18:53:19 -0800 (PST) Received: from smtp3.adl2.internode.on.net (smtp3.adl2.internode.on.net [203.16.214.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF39B43D2D for ; Mon, 1 Mar 2004 18:53:18 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from midget.dons.net.au (ppp39-208.lns1.adl1.internode.on.net [150.101.39.208])i222r8UK077437; Tue, 2 Mar 2004 13:23:09 +1030 (CST) Received: from inchoate.gsoft.com.au (root@localhost.dons.net.au [127.0.0.1]) by midget.dons.net.au (8.12.9/8.12.9) with ESMTP id i222r3YS074698; Tue, 2 Mar 2004 13:23:05 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: "Anton Karpov" , Date: Tue, 2 Mar 2004 13:22:57 +1030 User-Agent: KMail/1.5.4 References: <000701c3ff09$b5a20a70$0202a8c0@karputer> In-Reply-To: <000701c3ff09$b5a20a70$0202a8c0@karputer> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200403021322.58307.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.26 (www . roaringpenguin . com / mimedefang) Subject: Re: can't boot new kernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2004 02:53:19 -0000 On Monday 01 March 2004 07:49, Anton Karpov wrote: > This is a common question, maybe not suitable for this maillist, but I > would like to hear any ideas how to work it out. > Let suppose I build new world and kernel, reboot my current box, and new > kernel fails to boot (actually it hangs while detecting ata). So I should > to go into load prompt and type 'boot /boot/kernel.bak/kernel', whouldn't > I? Ok, I try to boot and old kernel but now it fails too (maybe because of > new world?). So now I'm without any working kernel. The only way I see to > solve this trouble is to compile a sutable kernel on another machine, boot > with installation/recovery cd, escape to recovery shell, mount root > partition and replace /boot/kernel/ with another one? Or does load prompt > can offer me any builtin feature to avoid using recovery live cd (cuz i > haven't neither such cd, nor another bsd box actually :) The point to rebooting into your new kernel after an upgrade is to allow you to back out if the kernel is hosed. ie if you boot your new kernel and it fails you can roll back to the old kernel. If the new kernel works you can then attempt installworld and run that. Unfortunately if installworld hosed your machine you are in for a tough time depending on badly it screwed things up :( What happens when you boot with your old kernel into the new world? If you have some semi-recent install media you can probably fix it by booting single user with the old kernel and mounting the CDROM, then unpacking the bin dist over your system. That presumes you can actually mount things with your kernel/userland combo which may or may not be true.. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5