From owner-freebsd-current Tue Jan 5 08:24:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02512 for freebsd-current-outgoing; Tue, 5 Jan 1999 08:24:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02507 for ; Tue, 5 Jan 1999 08:24:10 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id LAA49743; Tue, 5 Jan 1999 11:27:52 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Tue, 5 Jan 1999 11:27:52 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: "Thomas T. Veldhouse" cc: Blaz Zupan , freebsd-current@FreeBSD.ORG Subject: Re: Kernel cannot mount root with new bootblocks In-Reply-To: <00d001be38c6$200aeea0$236319ac@w142844.carlson.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Jan 1999, Thomas T. Veldhouse wrote: > In light of all the boot problems I have seen, are there still plans to go > ELF Kernel tomorrow? I think you will see that people are going to take a > wait and see aproach with CURRENT if this happens. Naw, lets have the commiters walking on eggshells supporting both targets until the next release. I'm sure they're really keen on that. :) I've noticed most all the problems people have been experiancing can be attributed to user error, not programming error, the boot blocks work fine and are extremely configuable. Unfortunatly the only documentation available at this point is this list archive. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message