From owner-freebsd-current  Mon Mar  9 21:20:59 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA14805
          for freebsd-current-outgoing; Mon, 9 Mar 1998 21:20:59 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14776;
          Mon, 9 Mar 1998 21:20:45 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA02316;
	Tue, 10 Mar 1998 16:17:41 +1100
Date: Tue, 10 Mar 1998 16:17:41 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199803100517.QAA02316@godzilla.zeta.org.au>
To: bde@zeta.org.au, jonny@coppe.ufrj.br
Subject: Re: *HEADS UP* Correction to previous postings.
Cc: current@FreeBSD.ORG, mike@smith.net.au, stable@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>// User actions in the 3 cases:
>// 1. Hope this doesn't happen.  It is very unlikely to happen for boot disks.
>
>Most PC BIOSes (if not all) will not boot from a disk if the first block
>does not have the 0xAA55 signature.    Indeed, they will not boot without
>a valid MBR.

The FreeBSD boot blocks can boot from any fd, wd, sd or wfd disk supported
by the BIOS.

>Have you ever seen such a case ?  Or does this discussion apply to

I probably have, but don't remember.  One of my systems loads the boot
blocks from wd0 and the boot blocks the kernel from sd0.  sd0 is
all-FreeBSD and would work with all-zeros in the MBR.

Bruce

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