From owner-freebsd-current@FreeBSD.ORG  Tue Nov 25 18:50:29 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1DE9016A4CF
	for <freebsd-current@freebsd.org>;
	Tue, 25 Nov 2003 18:50:29 -0800 (PST)
Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com
	[192.108.102.143])
	by mx1.FreeBSD.org (Postfix) with ESMTP id F068143FE3
	for <freebsd-current@freebsd.org>;
	Tue, 25 Nov 2003 18:50:27 -0800 (PST)
	(envelope-from wa1ter@myrealbox.com)
Received: from myrealbox.com wa1ter@smtp-send.myrealbox.com [66.126.110.249]
	$ on Novell NetWare	via secured & encrypted transport (TLS);
	Tue, 25 Nov 2003 19:50:32 -0700
Message-ID: <3FC41523.6060105@myrealbox.com>
Date: Tue, 25 Nov 2003 18:51:15 -0800
From: walt <wa1ter@myrealbox.com>
Organization: none
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031125
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: freebsd-current@freebsd.org
References: <bq0pep$gc8$1@FreeBSD.csie.NCTU.edu.tw>
In-Reply-To: <bq0pep$gc8$1@FreeBSD.csie.NCTU.edu.tw>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: How to fix this in 5.1-REL??
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Nov 2003 02:50:29 -0000

Brooks Davis answered:

walt asked:
>>What does 'buildworld' give us that the new kernel might need?

> The correct toolchain including the compiler and config(8).

Okay, thanks, that helps.

Just thinking out loud about worst-case examples for people who
do routinely use 'make world' (like I have for several years).

I found out first-hand why installworld quits halfway through
when the new executables won't run on the old kernel.  I need no
further education on that point ;-)

I'm thinking, though, that doing 'make kernel' first has a much
lower potential for disaster than 'make world':  if I reboot after
a 'make kernel' and the new kernel won't run on the old world, then
all I need to do to recover is to boot the old kernel again and
'make buildworld'. Seems difficult to do any real harm this way.

Is this completely wrong-headed?  Am I missing something important?

(Yes, I know I should just do it the right way every time -- but
I'm trying to reason through just why some ways are right and
some are wrong.)

Thanks for any insights.