From: arnold@skeeve.com (Aharon Robbins)
Subject: [TUHS] Bringing up any 4.3BSD on a MicroVAX without tape....
Date: Thu, 20 Oct 2005 09:36:52 +0200 [thread overview]
Message-ID: <200510200736.j9K7aqga003340@skeeve.com> (raw)
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
next reply other threads:[~2005-10-20 7:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 7:36 Aharon Robbins [this message]
2005-10-20 15:04 ` robertdkeys
2005-10-21 7:52 ` Jochen Kunz
-- strict thread matches above, loose matches on Subject: below --
2005-10-21 12:31 Jose R Valverde
2005-10-20 16:57 Michael Sokolov
2005-10-19 3:52 Michael Sokolov
2005-10-19 4:25 ` Gregg Levine
2005-10-19 17:28 ` robertdkeys
2005-10-15 15:49 [TUHS] Ancient unixes Gregg C Levine
2005-10-19 3:00 ` [TUHS] Bringing up any 4.3BSD on a MicroVAX without tape robertdkeys
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200510200736.j9K7aqga003340@skeeve.com \
--to=arnold@skeeve.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).