19 Oct
2005
19 Oct
'05
3:52 a.m.
robertdkeys(a)aol.com wrote:
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
19 Oct
19 Oct
4:25 a.m.
New subject: Bringing up any 4.3BSD on a MicroVAX without tape....
Hello from Gregg C Levine
I have here a DEC VAXstation 3100M76.
It is in the same boat as the one Robert is writing about. I know I
can install NetBSD/vax on it using the net boot concept. But I'd like
to run one of the appropriate distributions from "our" collection. Any
suggestions?
--
Gregg C Levine gregg.drwho8(a)gmail.com
"This signature was once found posting rude
messages in English in the Moscow subway."
On 10/18/05, Michael Sokolov <msokolov(a)ivan.harhan.org> wrote:
robertdkeys(a)aol.com wrote:
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
_______________________________________________
TUHS mailing list
TUHS(a)minnie.tuhs.org
http://minnie.tuhs.org/mailman/listinfo/tuhs
5:28 p.m.
New subject: Bringing up any 4.3BSD on a MicroVAX without tape....
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
6763
days inactive
6763
days old
2 comments
3 participants
participants (3)
-
Gregg Levine -
msokolov＠ivan.Harhan.ORG -
robertdkeys＠aol.com