From owner-freebsd-current Fri Mar 3 15: 5:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 7EF3D37B6C0; Fri, 3 Mar 2000 15:05:34 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id UAA27066; Fri, 3 Mar 2000 20:39:31 GMT (envelope-from nik) Date: Fri, 3 Mar 2000 20:39:28 +0000 From: Nik Clayton To: Jim Bloom Cc: Nik Clayton , current@FreeBSD.ORG Subject: Re: Kernel hangs booting fresh -current Message-ID: <20000303203928.A20369@catkin.nothing-going-on.org> References: <20000303014011.A754@catkin.nothing-going-on.org> <38BFB249.D675954E@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <38BFB249.D675954E@acm.org>; from Jim Bloom on Fri, Mar 03, 2000 at 07:38:33AM -0500 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 03, 2000 at 07:38:33AM -0500, Jim Bloom wrote: > 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. OK. That just about makes sense. > It is almost impossible to do forward compatibility on > major changes. I guess you need to update the handbook to reflect this > change. Not sure. As a corner case it should probably stay in UPDATING. N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message