From owner-freebsd-hackers  Tue Nov  5 03:53:07 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id DAA27268
          for hackers-outgoing; Tue, 5 Nov 1996 03:53:07 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA27263
          for <hackers@FreeBSD.org>; Tue, 5 Nov 1996 03:53:02 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id WAA03814; Tue, 5 Nov 1996 22:47:50 +1100
Date: Tue, 5 Nov 1996 22:47:50 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199611051147.WAA03814@godzilla.zeta.org.au>
To: karl@mcs.net, matt@lkg.dec.com
Subject: Re: Blargh - BSDI disk labels
Cc: hackers@FreeBSD.org
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>> FreeBSD doesn't understand BSDI disk labels.  Like at all.
>> 
>> There's no fix for this, is there?
>
>Here's a patch I made for 2.1.0 so I could mount my BSD/OS labels.
>It's ugly but it works...

It depends on the BSD/OS label having a 'c' partition that starts
at absolute offset 0 even when the BSD/OS slice doesn't start at
offset 0, right?  This is like the old FreeBSD 'd' partition.  How
are bad144 tables handled in BSD/OS?

Karl's problem was that the BSD/OS bootstrap on the MBR is incompatible
with a standard MBR.

Bruce