From owner-freebsd-current  Fri Mar  3  4:38:41 2000
Delivered-To: freebsd-current@freebsd.org
Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.251.241])
	by hub.freebsd.org (Postfix) with ESMTP
	id D8B5F37B7CF; Fri,  3 Mar 2000 04:38:34 -0800 (PST)
	(envelope-from bloom@acm.org)
Received: from acm.org (localhost [127.0.0.1])
	by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id HAA00860;
	Fri, 3 Mar 2000 07:38:33 -0500 (EST)
	(envelope-from bloom@acm.org)
Message-ID: <38BFB249.D675954E@acm.org>
Date: Fri, 03 Mar 2000 07:38:33 -0500
From: Jim Bloom <bloom@acm.org>
Reply-To: bloom@acm.org
X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Nik Clayton <nik@FreeBSD.ORG>
Cc: current@FreeBSD.ORG
Subject: Re: Kernel hangs booting fresh -current
References: <20000303014011.A754@catkin.nothing-going-on.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Nik Clayton wrote:
> 
> On a related note, why does UPDATING say to build and install the kernel,
> and then reboot, before doing the "installworld"?  That contradicts the
> advice in the Handbook (which I wrote), and I would've thought it's wrong
> precisely because it allows for things like kernel/mount mismatches to
> occur.

Because the signal interface changed several months ago.  If you ran
installworld on an old kernel, the machine would panic part way through
the install.  It is almost impossible to do forward compatibility on
major changes.  I guess you need to update the handbook to reflect this
change.

Jim Bloom
bloom@acm.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message