From owner-freebsd-questions@FreeBSD.ORG Wed Oct 11 09:38:34 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F7EE16A403 for ; Wed, 11 Oct 2006 09:38:34 +0000 (UTC) (envelope-from norgaard@locolomo.org) Received: from strange.daemonsecurity.com (59.Red-81-33-11.staticIP.rima-tde.net [81.33.11.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id B75AF43D46 for ; Wed, 11 Oct 2006 09:38:33 +0000 (GMT) (envelope-from norgaard@locolomo.org) Received: from [192.168.7.193] (68.Red-80-34-55.staticIP.rima-tde.net [80.34.55.68]) by strange.daemonsecurity.com (Postfix) with ESMTP id 42B1C2E037; Wed, 11 Oct 2006 11:38:32 +0200 (CEST) Message-ID: <452CBB91.3000402@locolomo.org> Date: Wed, 11 Oct 2006 11:38:25 +0200 From: Erik Norgaard User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Zbigniew Szalbot References: <20061011084014.W23849@192.168.11.51> In-Reply-To: <20061011084014.W23849@192.168.11.51> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: custom kernel, make buildkernel and then? 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: Wed, 11 Oct 2006 09:38:34 -0000 Zbigniew Szalbot wrote: > I have in the past used supfile with ports-all option and couldn't build > a custom kernel. Yesterday it dawned on me that I need sources for that, > not ports. So I ran cvsup with src-all option. Now, I followed these steps: > > # cd /usr/src/sys/i386/conf > # mkdir /root/kernels > # cp GENERIC /root/kernels/LISTS > # ln -s /root/kernels/LISTS The target directory for the build is /usr/obj, so in /usr/obj/usr/src/sys you can see what kernels have been built. Now BEWARE! One thing is the filename of the kernel config, another thing is the string set in the "ident" parameter in the config file. To stay sane, always change it to the same as the config file name. The ident is what the kernel reports it self to be, and a custom kernel should not claim to be a GENERIC kernel. And this may also determine where the kernel is built. So, if you didn't change the ident, then you may find you have a non-generic GENERIC kernel and # make installkernel will install that. But don't! Change the ident, rebuild your kernel and install the custom kernel. This is important, because if you later report a bug you are asked to submit the output of 'uname -a' and developers will think you are using a GENERIC kernel when in fact you are not. Cheers, Erik -- Ph: +34.666334818 web: http://www.locolomo.org X.509 Certificate: http://www.locolomo.org/crt/8D03551FFCE04F0C.crt Key ID: 69:79:B8:2C:E3:8F:E7:BE:5D:C3:C3:B1:74:62:B8:3F:9F:1F:69:B9