From owner-freebsd-questions@FreeBSD.ORG Mon Aug 20 13:13:54 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F050E106564A for ; Mon, 20 Aug 2012 13:13:53 +0000 (UTC) (envelope-from jamie@kode5.net) Received: from kontrol.kode5.net (kontrol.kode5.net [80.229.5.32]) by mx1.freebsd.org (Postfix) with ESMTP id 5BD2D8FC08 for ; Mon, 20 Aug 2012 13:13:52 +0000 (UTC) Received: from kontrol.kode5.net (localhost [127.0.0.1]) by kontrol.kode5.net (8.14.5/8.14.5) with ESMTP id q7KDDjtv029228 for ; Mon, 20 Aug 2012 14:13:45 +0100 (BST) (envelope-from jamie@kode5.net) Received: (from jamie@localhost) by kontrol.kode5.net (8.14.5/8.14.5/Submit) id q7KDDiqV029227 for freebsd-questions@freebsd.org; Mon, 20 Aug 2012 14:13:44 +0100 (BST) (envelope-from jamie@kode5.net) X-Authentication-Warning: kontrol.kode5.net: jamie set sender to jamie@kode5.net using -f Date: Mon, 20 Aug 2012 14:13:44 +0100 From: Jamie Paul Griffin To: freebsd-questions@freebsd.org Message-ID: <20120820131344.GA6963@kontrol.kode5.net> Mail-Followup-To: freebsd-questions@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: x-operating-system: FreeBSD 9.1-PRERELEASE amd64 x-pgp-fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38 User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: Issue with kernel building X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2012 13:13:54 -0000 == Michael Powell wrote on Sun 19.Aug'12 at 19:43:14 -0400 == > Keep in mind whenever you install a new kernel your present kernel (and its > matching modules) get moved to kernel.old. What this means is that the > GENERIC you have with a base install will be moved to kernel.old and can be > used in the event the new kernel won't boot. Realize this: after the next > rebuild process this kernel.old will be replaced _again_. In which case you > might now have 2 broken kernels with not an easy way to recover. Very good point! I'd clear the /usr/src/obj directory as pointed out, then build a generic kenel, install it and boot from it. Then you know you've got a working kernel to fall back on. At that point rebuild your custom kernel with correct commands as pointed out in the previous response by Michael; i.e. `make buildkernel KERNCONF=MYKERNEL` ... etc.