From owner-freebsd-current@FreeBSD.ORG Mon Mar 1 05:17:18 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 A4A4216A4E3 for ; Mon, 1 Mar 2004 05:17:15 -0800 (PST) Received: from mtaw4.prodigy.net (mtaw4.prodigy.net [64.164.98.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18EB243D1D for ; Mon, 1 Mar 2004 05:17:15 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (f9ae6c0c1d887202769c85bd699f2659@adsl-67-119-53-203.dsl.lsan03.pacbell.net [67.119.53.203]) by mtaw4.prodigy.net (8.12.10/8.12.10) with ESMTP id i21DH9Tw003071; Mon, 1 Mar 2004 05:17:11 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id AD7DE54B58; Mon, 1 Mar 2004 05:16:37 -0800 (PST) Date: Mon, 1 Mar 2004 05:16:36 -0800 From: Kris Kennaway To: Anton Karpov Message-ID: <20040301131636.GA52938@xor.obsecurity.org> References: <000701c3ff09$b5a20a70$0202a8c0@karputer> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PNTmBPCT7hxwcZjr" Content-Disposition: inline In-Reply-To: <000701c3ff09$b5a20a70$0202a8c0@karputer> User-Agent: Mutt/1.4.1i 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: Mon, 01 Mar 2004 13:17:18 -0000 --PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Mar 01, 2004 at 12:19:24AM +0300, 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 :) You need to get a working kernel onto that machine somehow. This is the same question as "What are the different ways of booting a FreeBSD kernel?". There are lots of possibilities, including floopies, CDs, tftp booting, NFS booting, PXE booting, and probably others I have forgotten. See the handbook for more information. Kris --PNTmBPCT7hxwcZjr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAQzezWry0BWjoQKURAtvdAJ9BgVYxdRfWfD5sUSgr8/aPRs51KQCg78oT 1R7iv8Xca8/pQz30Rsi4fX0= =ndGd -----END PGP SIGNATURE----- --PNTmBPCT7hxwcZjr--