From owner-freebsd-doc Tue Jul 11 9:35:40 2000 Delivered-To: freebsd-doc@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 42DC537B5F9; Tue, 11 Jul 2000 09:35:37 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id 0226B1460; Tue, 11 Jul 2000 09:31:17 -0700 (PDT) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) with ESMTP id JAA00481; Tue, 11 Jul 2000 09:31:17 -0700 (PDT) Message-ID: <396B4BD5.37D75900@cup.hp.com> Date: Tue, 11 Jul 2000 09:31:17 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Brad Knowles Cc: doc@freebsd.org, grog@lemis.com, khera@kciLink.com, Kris Kennaway , "Chad R. Larson" Subject: Re: HEADS UP! Always use the 'make buildkernel' target tomake yer kernels References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brad Knowles wrote: > installed. Therefore, the only safe way to build a kernel on such a > machine is to do the following: > > make buildworld > make buildkernel > make installkernel > shutdown (drop into single-user mode) > make installworld > mergemaster > reboot As pointed our by Sheldon: reboot before doing an installworld. The reason is that when you upgrade, binaries you're installing may not run on an older kernel. This will be fixed soon, but in the mean time I suggest people reboot. > These steps require that you have defined "KERNEL=WHATEVER" > in /etc/make.conf. If you have not, you will need to add > "kernel=WHATEVER" to the "make installkernel" command above. Make that KERNEL=WHATEVER. Also note that it is allowed to have KERNEL="FOO BAR BAZ" and that if you have this in make.conf, you'd better make sure you give yourself a change to override it on the commandline (ie have KERNEL?="FOO BAR BAZ" in make.conf) > However, if you have problems, you should try re-running this > process with "config -r WHATEVER" to clean out the remnants of the > old build tree and to eliminate any potential cruft. Do not report > problems to the mailing lists with kernels you have built, if you > have not configured them with "config -r". You probably want to add a paragraph that says if it still fails, try using buildkernel after a buildworld. The latter is important, because the failing of the kernel build might be due to a change in tools. > Note that the steps given in #1 above will install a copy of the > GENERIC kernel. If you have a customized kernel, you'll need to > follow those instructions to safely install the GENERIC kernel, and > then follow the steps in #2 above to install your customized kernel. This doesn't make sense. You already said that #1 can be modified for those with custom kernels, right? > Also note that if you run into problems anywhere along any part > of either of these processes, ensure that you are not passing the > "-j4" (or any other "-j#" argument) to make. If you are, then start > over from the beginning, this time omitting the "-j4" argument (which > causes a parallel make). While using "-j4" usually works, there are > sometimes problems with it. Do not report any problems to the > mailing lists with a "make world", "make buildworld", or a kernel > build that was done with a "-j4" (or any similar) argument passed to > make. I don't think we should throw this in. -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message