bush@evax.arl.utexas.edu (Joe Bush) (05/30/90)
In the hope that other novices might find this useful and the more experienced Ultrix wizards won't find this too insulting, I would like to summarize the method I used to successfully configure secondary swap space. On a uVAX 3900 w/32Mb of core running Ultrix 3.1 with primary swap on ra0, and adding "two" secondary swap partitions, each on a separate drive (ra1 and ra2 in this case), the following procedure worked well: 1. add the following lines to /etc/fstab /dev/ra1b::sw:0:0:ufs:: /dev/ra2b::sw:0:0:ufs:: 2. add the following line in /sys/conf/HOSTNAME config vmunix root on ra0a swap on ra0b and ra1b \ and ra2b dumps on ra0b 3. rebuild kernel 4. reboot Note: On step (3) be sure to copy the new kernel to /vmunix Neglecting this little detail was the cause of all my earlier woes (ie., the "no such device" errors). Note: On step (1) file-system types other than "ufs" may work but I did not experiment with any. One wizard suggested that *some* PD software may prefer the string "swap" in this field. Note: On step (4) the "swapon -a" command found in /etc/rc performs the addition of secondary swap at boot time according to /etc/fstab and echoes this success or failure of this action to the console. Since swap space is NOT "mounted" like an ordinary Ultrix filesystem, it does NOT show up under the "df" command. The "pstat -s" command can be used to verify a successful configuration. Thanks to *all* for the help and assistance. - Joe -- bush@evax.arl.utexas.edu Vax Systems Manager (817) 273 - 3333 CSE Dept. UT-Arlington Office Rm 221 EB2 403 South Cooper P.O. Box 19015 Arlington, Texas 76019