🚀 go-pugleaf

In article <42pr0l$uhk@zippy.cais.net> jsdy@cais3.cais.com (Joseph S. D. Yao) writes:

   przemek writes:
   >Warning: the following is untested. 
	...
   > Now you need to reset lilo so that it can boot from the second disk too: 
   > add an appropriate section to /etc/lilo.conf. Reboot and check that
   > you can indeed boot Linux on the second drive

   Warning: if I read the original and Przemek's response correctly, then
   it doesn't quite work, the way Przemek described it, because of some
   peculiarities of LILO (which I assume you're using to boot).  Copying -
   OK; but check that you can boot Linux off the new drive BEFORE you
   re-partition the old one.  Check that you REALLY REALLY are booting off
   the new drive: watch the LEDs on the old drive, and make sure that it
   isn't still crucial to the boot process.  I'll write up the problems I
   had doing similar things soon, when I get a chance, including odd code
   to fix same.

Of course Joe is right that you have to be careful and doublecheck
everything, but I think newer versions of LILO can be instructed to
boot off second disk while still booted from the first disk. All it
took was an additional entry in /etc/lilo.conf pointing it to get the
kernel image from wherever /dev/hdb2 was mounted (/mnt/zImage in my
case). It is true that after booting the real mounted location will be
different because your root will be mounted on /dev/hdb2, so now the
same kernel image will be /zImage, but LILO only needs it to record
device/sector information and store it in MBR of the first disk.

--
			przemek klosowski (przemek@nist.gov)
			Reactor Division (bldg. 235), E111
			National Institute of Standards and Technology
			Gaithersburg, MD 20899,      USA

			(301) 975 6249