From owner-freebsd-hackers Mon Jun 2 12:03:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA05932 for hackers-outgoing; Mon, 2 Jun 1997 12:03:18 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA05916 for ; Mon, 2 Jun 1997 12:03:15 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id MAA07091; Mon, 2 Jun 1997 12:02:32 -0700 (PDT) To: hal@vailsys.com (Hal Snyder) cc: Thomas David Rivers , hackers@FreeBSD.ORG Subject: Re: What's wrong with a bootable CDROM??? In-reply-to: Your message of "Mon, 02 Jun 1997 17:58:51 GMT." <33c60885.2694307599@w3> Date: Mon, 02 Jun 1997 12:02:32 -0700 Message-ID: <7087.865278152@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Can the CD boot code look at HD partition table(s) and display a prompt > if it finds a bootable [BSD] system? If you specify CD boot at the > prompt, ok; if timeout, boot from HD. Uh.. I think there is some confusion about how this works. :-) The bootable CD just looks like a floppy, transmogrified into one by the BIOS before FreeBSD's boot code ever gets run. There's no difference between booting the CD and booting a floppy which has been created from the boot.flp image. As I told TDR, if it annoys you then simply turn it off! :) Jordan