From owner-freebsd-current@FreeBSD.ORG Sun Feb 29 15:23:35 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 9862816A4CE for ; Sun, 29 Feb 2004 15:23:35 -0800 (PST) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DBCA43D39 for ; Sun, 29 Feb 2004 15:23:35 -0800 (PST) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (localhost [127.0.0.1]) i1TNNONv057241; Sun, 29 Feb 2004 18:23:24 -0500 (EST) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)i1TNNO8q057238; Sun, 29 Feb 2004 18:23:24 -0500 (EST) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Sun, 29 Feb 2004 18:23:24 -0500 (EST) From: Andre Guibert de Bruet To: toxa In-Reply-To: <002701c3ff0f$75c653b0$0202a8c0@karputer> Message-ID: <20040229181600.O52152@alpha.siliconlandmark.com> References: <002701c3ff0f$75c653b0$0202a8c0@karputer> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: freebsd-current@freebsd.org 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: Sun, 29 Feb 2004 23:23:35 -0000 On Mon, 1 Mar 2004, toxa 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 You're off of the beaten path. If the kernels are not 100% ABI-compatible, you're most likely going to run into problems. The official fail-safe (well, much safer at least) way to upgrade is to make buildworld, buildkernel, installkernel, reboot into single-user mode, mount -a and then (and only then!) installworld. > 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 :) You're best off doing a binary upgrade of just the base system over your current install. This is the easiest way to recover from this type of foot-shooting. Regards, Andy > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ >