From mboxrd@z Thu Jan  1 00:00:00 1970
From: arnold@skeeve.com (Aharon Robbins)
Date: Thu, 20 Oct 2005 09:36:52 +0200
Subject: [TUHS] Bringing up any 4.3BSD on a MicroVAX without tape....
Message-ID: <200510200736.j9K7aqga003340@skeeve.com>

Wasn't there an "installboot" program that told the bootblock where
to find the /boot file?

Boy was it a lllloooonnnngggg time ago that I dealt with this stuff.

Arnold

> Date: Wed, 19 Oct 2005 13:28:31 -0400
> From: robertdkeys at aol.com
> Subject: Re: [TUHS] Bringing up any 4.3BSD on a MicroVAX without tape....
> To: msokolov at ivan.Harhan.ORG, tuhs at minnie.tuhs.org
>
>  The /boot is there, so it is somewhere between the bootblocks
> and /boot that the connection is lost.  The /boot is apparently
> not correctly found.  But, it is there......
>  
> Bob Keys
>  
> -----Original Message-----
>
> > The problem is that it won't install boot blocks that work.
> > None of the raboot/rdboot/bootra/bootrd combos get
> > any farther than the cryptic "loading boot" message.
>
> The "loading boot" message comes from the bootblock code and indicates
> that the bootblocks are good and working.  If it stops there, it means
> that you are missing the /boot file in the root filesystem (that's what
> it's loading).
>
> MS