Sys V installation problems

[Joseph S. D. Yao]

In article <1209 at brl-tgr.ARPA> eichelbe at nadc.arpa writes:
>	Has anyone been able to install Sys V.2.2 on a VAX 11/780 without
>having an RP06, RM05, RM80, or an RP07 at NEXUS 8 (MBA 0) ?

Because of a bug in the boot code  l e n g t h , if they are using the
s5r2v2 boot block you cannot boot with an RM80 or an RP07, either!  The
table at the end of the block gets truncated.  However, I believe that
they have the s5r2v1 or s5r1v2 boot block on the tape.

Fix:  delete all the code that checks sash's header, since it does not
have one!  I.e. (roughly):
	:/# r0 is cleared by the movc5 instruction/+1;/exec:/-1d

>(2) We use the VAX to run 4.1 BSD when we're not struggling late at night to
>    bring up things like Sys V.  The 4.1 BSD system likes everything just where
>    it is.
>    Ideas, suggestions?

Jon,

I booted s5r2.0v2 using s5r2.0v1, because it was more convenient that
way.  (It turned out that the above bug would've caught the RP07 any-
way.)  I booted Ultrix 1.0 using BSD4.1c because I couldn't do it with
the Ultrix boot tape, and 1.1 using 1.0 because it was convenient.  I
suggest you boot s5r2v2 using BSD4.1 by simply dd'ing the root image
onto an rm03; and then if you can't boot from that or mount that and
compile a new Unix (the SysV and BSD4.1 FS's are quite similar),
"just" read in the /usr/src/uts stuff from the /usr tar tape, monkey
the dfile and the makefiles to allow you to compile it the way you
want it, and boot the new unix from your 4.1.  From there, you're on
your way!
-- 

	Joe Yao		hadron!jsdy at seismo.{CSS.GOV,ARPA,UUCP}