From owner-freebsd-current  Tue Jan  5 09:15:25 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA08455
          for freebsd-current-outgoing; Tue, 5 Jan 1999 09:15:25 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08447
          for <freebsd-current@FreeBSD.ORG>; Tue, 5 Jan 1999 09:15:24 -0800 (PST)
          (envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
	by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id JAA05743;
	Tue, 5 Jan 1999 09:14:19 -0800 (PST)
To: "Thomas T. Veldhouse" <veldy@visi.com>
cc: "Alfred Perlstein" <bright@hotjobs.com>, "Blaz Zupan" <blaz@gold.amis.net>,
        freebsd-current@FreeBSD.ORG
Subject: Re: Kernel cannot mount root with new bootblocks 
In-reply-to: Your message of "Tue, 05 Jan 1999 10:11:58 CST."
             <00d001be38c6$200aeea0$236319ac@w142844.carlson.com> 
Date: Tue, 05 Jan 1999 09:14:19 -0800
Message-ID: <5740.915556459@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 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.

That's never a bad idea with -current anyway.  People have gotten
too complacent. :)

- Jordan

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