From owner-freebsd-stable Wed Jan 12 9:32:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles556.castles.com [208.214.165.120]) by hub.freebsd.org (Postfix) with ESMTP id 9449214E39; Wed, 12 Jan 2000 09:32:52 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA02551; Wed, 12 Jan 2000 09:39:31 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001121739.JAA02551@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Bristow Cc: Mike Smith , R Joseph Wright , freebsd-stable@freebsd.org Subject: Re: fbsdboot.exe can't load elf kernels In-reply-to: Your message of "Wed, 12 Jan 2000 17:07:04 GMT." <20000112170704.A5073@lindt.urgle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Jan 2000 09:39:31 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I still maintain that the /right/ solution is for the BIOS to have > a ``while booting shovel data out COM1 and accept data from COM1 as if > it were my keyboard'' option. > > I've seen them on (I think) NCR boxes. Intel do this on their server boxes, to the extent that if you have a colour ANSI terminal you can run fullscreen expansion BIOS tools like eg. Adaptec's. I'm reasonably sure that it's just an extra-price option from the major BIOS vendors. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message