From owner-freebsd-hackers Fri May 22 12:33:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28553 for freebsd-hackers-outgoing; Fri, 22 May 1998 12:33:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28512 for ; Fri, 22 May 1998 12:33:36 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.8/8.8.8) with UUCP id VAA11341; Fri, 22 May 1998 21:31:50 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id VAA25522; Fri, 22 May 1998 21:29:59 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199805221929.VAA25522@semyam.dinoco.de> To: freebsd-hackers@FreeBSD.ORG Cc: joelh@gnu.org, seggers@semyam.dinoco.de Subject: Re: Problem resolutions... In-reply-to: Your message of "Fri, 22 May 1998 11:31:00 CDT." <199805221631.LAA22234@detlev.UUCP> Date: Fri, 22 May 1998 21:29:59 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > First 'make world', then kernel. Almost always true. (There may be > > specific cases where you should get away from the kernel because it eats > > filesystems or something...) > > Why is that? I would expect some execs to depend on kernel features, > not vice versa. For building a new kernel you get a directory named like your kernel config file - usually under /usr/src/sys/compile/CONFIG_FILE_NAME. Creating this involves generating some C header files from the entries in your kernel config file and this is what /usr/sbin/config does. Now comes the tricky part. Lets suppose - like it happened lately with the CAM devices table - that the kernel sources need something in these generated header files which only a new /usr/sbin/config knows about. It works when you first do a "make world" or at least make a new config program (the new and more knowledgeable /usr/sbin/config is around then) but the computer won't be able to do it the other way round. User programs that "make world" creates sometimes depend on new kernel (new features, changed structures and so on) and those won't work in part or even in whole before you have a new kernel running. Usually what's missing is some new functionality or some program that you don't need for compiling and installing a new kernel. No loss as you are in single user mode by then as "make installworld" in multi user mode might cause severy confusion and a few minutes later you have a new kernel up and running (hopefully - sometimes bugs get in the way) anyway. Stefan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message