Jonathan Engdahl wrote:
Here are the first couple questions:
At boot-up, right after it tells me about how much memory I have, it
starts spitting gibberish. If I tell Kermit (my console) to switch to
7 bits even parity, I can read stuff again. It appears that the OS is
changing the line parameters. Does this make sense? If so, where do I
find the file with this config in it? I grepped for "stty" in / and
/etc but didn't find anything useful looking.
Yes this is to be expected. The console should be 7 bits. You can set
parity to "ignore".
I still can boot RT-11 from the floppy, but when I try
to boot UNIX
from the hard drive it halts. I did "dd if=/mdec/rauboot of=/dev/ra0a
count=1" per Steve Schultz's instructions, but it still won't boot. I
can download Warren's boot.dd via VTserver, and type "ra(0,0,0)unix",
and UNIX starts right up, so the only problem is the boot sector. It
used to boot RT-11 from hard drive fine, before I clobbered it with
UNIX. The only catch is that I have to toggle HALT and say "171000G"
(there's a boot ROM on the disk controller) because the CPU boot ROMs
at 173000 are some goofy DECserver stuff. Any ideas?
You must use the raw disk device as the output file in the dd command:
dd if=/mdec/rauboot of=/dev/rra0a count=1
Note two r's in the disk device name.
I partitioned the hard drive with 4.5 meg at ra0a, 4
meg at ra0b, and
the rest at ra0d. Was I supposed to disklabel ra0d as "2.11BSD" or
leave it "unused" -- the instructions didn't say. When I try to newfs
to /dev/ra0d, it gives me "not a character device". Here's ra0d:
You must run mkfs against the raw disk device, which is a character
device as opposed to the normal block device. You always run mkfs, or
fsck against the raw disk device, but you mount the block device. For
your system, /dev/ra0d is the block device, where /dev/rra0d is the raw
device.
ls -l /dev/ra0d
brw-r----- 1 root 5, 3 Sep 7 1987 /dev/ra0d
Note the "b" at the front of the permissions, which indicates that this
is a block device. Try "ls -l /dev/rra0d".
I need a way to download the rest of the UNIX tar files over the
console line. VTserver's documentation sort of stops after
booting up the root image. Where do I go from here? Is there
some built-in way of using a serial line driver like a tape, such as
"tar xvf /dev/tty"?
The tar command can take its input from any device that looks like a
file or from the standard input. I have not tried to use VTserver in
that way. Kermit would be another choice, but comes installed in
/usr/new on 2.11 BSD and you don't yet have /usr restored.
--
Doug Carman
pdp11(a)bellsouth.net