Path: utzoo!attcan!uunet!husc6!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!ut-sally!utastro!opal From: opal@utastro.UUCP (Chet Opal) Newsgroups: comp.os.vms Subject: Re: LAVC: uVAX II / RD53 as bootnode Message-ID: <2794@utastro.UUCP> Date: 21 Jun 88 00:07:34 GMT References: <8806201951.AA14806@ucbvax.Berkeley.EDU> Organization: U. Texas, Astronomy, Austin, TX Lines: 47 In article <8806201951.AA14806@ucbvax.Berkeley.EDU>, S211KENO@HTIKUB5.BITNET writes: > On the very first page of the VMS Local Area VAXcluster manual > is stated that a Microvax II bootnode must have a RD54 or larger system > disk. > And the VMS 4.6 KITINSTAL.COM refuses to install VMS 4.6 on a RD52 or RD53 > systemdisk if the Microvax II is a LAVC bootnode. > Why ? > Is it just a performance issue, is it just Digital trying to sell more > expensive disk-units or is there a serious reason like Satellite nodes > not being able to boot from a remote RD53 ? > Any comments on or experiences with Microvax/RD53 serving as LACV bootnode > are welcome. > I have successfully installed VMS 4.6 over MicroVMS 4.7 on an RD53 with two satellite nodes. Performance is not an issue; disk space is. You will need to either put the paging/swapping files for the satellites on their own disks (if they have them) or on a second disk on the boot node. My procedure was the following: 1) Break down the installation tape by $ COPYing the save_sets to a disk, then restore the first save_set to a disk directory. You will find the file KITINSTAL.COM, which you will need to edit. 2) Search for the section containing a reference to "RD54", and comment out the lines which test for it. 3) Search for the section referring to VMS4.6, and if you are running 4.7, add that to the logical statement (or comment the whole thing out) 4) There was one more thing involving a file which it wanted which would only have been there if you had already installed clusters. I will try to find a DIFFERENCES file on KITINSTAL.COM; I know I made one...and will post it to the net. Anyway, you comment that check out also. 5) Reassemble the first saveset by backing it up to a disk file. 6) Recopy the bunch of modified savesets to a new TK50, or if there is room, you can copy they to DUA0:[0,0] and run VMSINSTAL on them from there (much, much faster than a TK50). Voila' Chet Opal, ascendant VMS guru. (MUCHO faster).