From owner-freebsd-current@FreeBSD.ORG  Tue Nov 25 15:35:13 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 0AFB516A4CE
	for <freebsd-current@freebsd.org>;
	Tue, 25 Nov 2003 15:35:13 -0800 (PST)
Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com
	[192.108.102.143])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 418DC4400B
	for <freebsd-current@freebsd.org>;
	Tue, 25 Nov 2003 15:35:11 -0800 (PST)
	(envelope-from wa1ter@myrealbox.com)
Received: from myrealbox.com wa1ter@smtp-send.myrealbox.com [66.126.109.8]
	$ on Novell NetWare	via secured & encrypted transport (TLS);
	Tue, 25 Nov 2003 16:35:13 -0700
Message-ID: <3FC3E75A.1010103@myrealbox.com>
Date: Tue, 25 Nov 2003 15:35:54 -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: <bq01p7$1u4r$1@FreeBSD.csie.NCTU.edu.tw>
In-Reply-To: <bq01p7$1u4r$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: Tue, 25 Nov 2003 23:35:13 -0000

Kevin Oberman wrote:

> ...Because changes are applied that will allow smooth upgrades
> when the kernel is built after the new system is built, but before it is
> installed, "make world" is increasingly unlikely to work...

The recent statfs changes demonstrated why the 'makeworld' > 'makekernel'
sequence sometimes fails  :-(

But I'm still very fuzzy on why the 'makekernel' > 'makeworld' sequence
is not recommended in FreeBSD the way it is, for example, in OpenBSD.

What does 'buildworld' give us that the new kernel might need?  Just a
simple example would help me more than anything.

Thanks.