ji@read.cs.columbia.edu (John Ioannidis) (05/11/89)
In article <8905011601.AA08948@natinst.com> you write: >X-Sun-Spots-Digest: Volume 7, Issue 273, message 19 of 23 > [Description of how the author tried to boot from xd1 after cloning > xd0 on it and ended up with root and swap on xd0] The kernel (/vmunix) that you had on xd1a was either a generic kernel or a `config vmunix root on xd swap on xd' kernel. The boot program correctly loaded vmunix from xd1's root partition, but after the kernel was given control, it used the first device that matched the config file specification, namely xd0a nad xd0b respectively. To make it boot off of xd1 without resorting to b -a, make a new kernel whose config clause is config vmunix root on xd1 swap on xd1 and put that in xd1a's /vmunix (don't replace /vmunix in the original root disk, xd0a). Now, if you boot from xd(0,1,0) either manually or by setting it as the default path using eeprom(8), you should get your root and swap filesystems on xd1a and xd1b respectively. Also, make sure that /etc/fstab on xd1a contains the proper entries for /, /usr etc. (/dev/xd1a / 4.2 rw 1 1 etc), otherwise you are in for a surprise after fsck is done. /ji #include <appropriate disclaimers> In-Real-Life: John Ioannidis E-Mail-To: <ji@cs.columbia.edu> P-Mail-To: 450 Computer Science, Columbia University, New York, NY 10027 V-Mail-To: +1 212 854 5510 ... It's all greek to me
beau@ames.arc.nasa.gov (05/17/89)
--> Among other things, I was trying to clone our boot disk (xd0) onto xd1.
--> After I set things up (ran installboot, etc.), I halted. In the monitor,
--> I set up the eeprom to boot off of xd(0,1,0). Fine. I booted, and it got
--> vmunix off of xd1, as expected. But it suddenly decided to use the root
--> and swap off of xd0:
In the kernel configuration file, there is a line that says (by default):
config vmunix swap generic
That tells the kernel to look for its root and swap on the "standard" set
of devices, in the Sun-defined default search order, and to use the first
one it finds, usually "disk0a" and "disk0b".
To run entirely off an alternate drive, you need to configure the kernel
explicitly for that drive. For example:
config vmunix root on xd1a swap on xd1b dumps on xd1b
You will end up with a slightly different kernel on each bootable device.
Beau James beau@Ultra.COM
Ultra Network Technologies {sun,ames}!ultra.com!beau