From owner-freebsd-bugs  Sat Jun 17 02:34:06 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id CAA15789
          for bugs-outgoing; Sat, 17 Jun 1995 02:34:06 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA15782
          for <bugs@FreeBSD.org>; Sat, 17 Jun 1995 02:34:01 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id RAA18958; Sat, 17 Jun 1995 17:57:56 +1000
Date: Sat, 17 Jun 1995 17:57:56 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199506170757.RAA18958@godzilla.zeta.org.au>
To: bde@zeta.org.au, hlew@genome.Stanford.EDU
Subject: Re: 2.05R panics on boot
Cc: bugs@FreeBSD.org
Sender: bugs-owner@FreeBSD.org
Precedence: bulk

>> Only one case can't possibly work: loading the bootstrap off a floppy
>> and then attempting to boot from a hard disk (e.g., by typing
>> sd(1,a)/kernel).  The boot code doesn't know about DM, so it won't
>> work if DM needs to be loaded.
>> 

>Right now the only way I can boot up FreeBSD system on the Ontrack DM 
>system is by using boot.flp and entering wd(1,a)/kernel.  This is very 
>annoying.  I have not tried and I doubt if I can access the msdos stuff 
>from FreeBSD for now.  

This seems to be the case that I said can't work.  Apparently wd1 doesn't
have Ontrack on it, but Ontrack on the boot disk adjusts for all disks.

Bruce