From owner-freebsd-current Sat Mar 14 02:09:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13676 for freebsd-current-outgoing; Sat, 14 Mar 1998 02:09:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13640 for ; Sat, 14 Mar 1998 02:09:17 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id CAA07633; Sat, 14 Mar 1998 02:08:01 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Studded cc: Matthew Thyer , FreeBSD CURRENT Subject: Re: trouble booting In-reply-to: Your message of "Fri, 13 Mar 1998 17:12:06 PST." <3509D966.DAE44397@dal.net> Date: Sat, 14 Mar 1998 02:08:01 -0800 Message-ID: <7629.889870081@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm curious about this. This isn't a dig, although my incredulity might > make it seem so. Every piece of documentation I've seen says to do it > the other way around. Make world first, then build kernel, then boot. This is correct. If you've just done major things to the build tools, or even if you've merely changed config(8) in a way that will blow out a new kernel (and this happens fairly often, actually) the make world will fix this for you before you move on to building the kernel. Also, building just the kernel and then rebooting from it (otherwise, what would be the point of building it first?) can truly hang you if your LKMs are out of date. Building the kernel first is therefore NOT recommended practice. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message