mp@andante.UUCP (Mark Plotnick) (10/20/88)
There have been times when, after a disk or controller or v-master
reconfiguration, we have problems locating the root filesystem or
backup root filesystems (either because of inadvertent errors such as
the disks getting moved around to different controllers or having their
drive numbers change, or because a filesystem or two gets smashed
because the new boards are defective).
It would be useful to be able to boot vmunix off of the console rl,
just to see the output of the autoconf stuff. Is there a way to
massage vmunix to be a standalone program that can be loaded with
>>>LOAD, or is there a standalone driver for the console rl so that
'boot' can read in a file from the rl's rt11 filesystem?
Mark Plotnick
allegra!mpchris@mimsy.UUCP (Chris Torek) (10/20/88)
In article <12934@andante.UUCP> mp@andante.UUCP (Mark Plotnick) writes: >It would be useful to be able to boot vmunix off of the console rl, >just to see the output of the autoconf stuff. Is there a way to >massage vmunix to be a standalone program that can be loaded with >>>>LOAD, or is there a standalone driver for the console rl so that >'boot' can read in a file from the rl's rt11 filesystem? Writing the latter might be a good idea, but in any case, the former is easy, if a trifle slow: nm /vmunix | egrep 'T start' which will give you the entry point (needed below); then cd /tmp cp /vmunix v strip v dd if=v of=vmunix bs=32 skip=1 rm v arff rvmf /dev/crl vmunix You can then >>>LOAD VMUNIX/ST 0 and >>>ST <entry> where <entry> is the entry point found by nm, stripped of the high bit (e.g., 80001614 => 1614). -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163) Domain: chris@mimsy.umd.edu Path: uunet!mimsy!chris