The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: robertdkeys@aol.com (robertdkeys@aol.com)
Subject: [TUHS] Bringing up any 4.3BSD on a MicroVAX without tape....
Date: Tue, 18 Oct 2005 23:00:34 -0400	[thread overview]
Message-ID: <8C7A270687203DA-1120-B77@MBLK-M39.sysops.aol.com> (raw)
In-Reply-To: <001501c5d1a0$07ea5f20$6501a8c0@who7>

Hello to the list, from a lurker, supposedly retired, but....
having run across one last MVIII crate for a lowly buck,
in surplus..... you know the rest.   It just has to run some
form of ancient BSD again.....(:+}}.....

Anyway, it is sans tape, and all my TK50 cartridges have
decomposed to dusty oxide, so it will have be resurrected
from something other than tape.

As luck has it, it has a scsi controller, and I happened to
have a scsi floppy from a decishbox long since gone to
the great bit crusher in the sky.  So, with some prodding
it booted off a NetBSD 1.4.1 vax floppy and was made
to run NetBSD 1.4.3 as a starter, to get the rest of the
early BSD bits onto the machine.  After making fsck trip
all over itself, and pushing some Tahoe and Reno bits
onto it, it now RUNS Tahoe (q0c variety) or Reno (archive
variety) quite happily.

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 machine locks up hard then.  Yet, I can boot and run
things fine off a NetBSD 1.1A VAX tk50 boot file ("stand")
dd'd to that lonely scsi floppy off the far end of the bus,
with the usual b/3 duaX.... followed by "ra0a" as the root
and ^D to multiuser baby.  Years ago, the first time around,
I had this working fine, but, when I backed up the then
running system, I forgot (like a dummy) to dd off a set of
working boot blocks or a working bootable root.  Ahh, stupid
me.....(:+}}.....

The nearest that I can tell is that it is not writing (using the
disklabel executable) a correct set of block addresses to
find the real /boot and kernel.  Once, however done, the
kernel is actually loaded, it runs fine (like off NetBSD tape
boot "stand").

Any of you old timers got any thoughts as to where my suite
is going afoul of the real way?  It is probably something quite
simple, but, my greymatters just can't seem to get it figured
out.  Any insights are appreciated.

Thanks!

Bob Keys
Olde Pfarte with too many VAXentoyz.....(:+}}.....





  parent reply	other threads:[~2005-10-19  3:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051015.085932.17381905.imp@bsdimp.com>
2005-10-15 15:02 ` [TUHS] Ancient unixes Brantley Coile
2005-10-15 15:49   ` Gregg C Levine
2005-10-15 21:55     ` Brantley Coile
2005-10-19  3:00     ` robertdkeys [this message]
2005-10-19  3:52 [TUHS] Bringing up any 4.3BSD on a MicroVAX without tape Michael Sokolov
2005-10-19  4:25 ` Gregg Levine
2005-10-19 17:28 ` robertdkeys
2005-10-20  7:36 Aharon Robbins
2005-10-20 15:04 ` robertdkeys
2005-10-21  7:52   ` Jochen Kunz
2005-10-20 16:57 Michael Sokolov
2005-10-21 12:31 Jose R Valverde

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=8C7A270687203DA-1120-B77@MBLK-M39.sysops.aol.com \
    --to=robertdkeys@aol.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).