Having another Linux installation on another disk
I have just installed another disk, sdc, on my SuSE Linux 7.3 system. I have installed Red Hat 7.3 on it, since I need to test some software I am writing. I need to be *absolutely* sure it works with the libs that come with RH7.3. After the RH7.3 installation, I restored my lilo, so that the system booted as before, and the RH7.3 installation was just lying there on sdc. So, how do I make lilo understand the new situation? The new disk has been partitioned as follows: sdc1 /boot sdc2 swap sdc3 / I intend not to let the two installations "see" each other, but I temporarily mounted /dev/sdc1 on /newdisk and ran /sbin/lilo with the /etc/lilo.conf below. This didn't work. I can boot to SuSE 7.3, but when I try booting to RH7.3, I just see: Booting Red Hat 7.3......... and nothing more happens. Something must be wrong with my /etc/lilo.conf entry for the new installation, but what? Is it that just temporarily mounting the /dev/sdc1 and running /sbin/lilo won't work? My /etc/lilo.conf looks like this, now: ///////////////////////////////////////////////////////////////// append="hdc=ide-scsi noapic" boot=/dev/hda disk = /dev/hda bios = 0x80 disk = /dev/sr0 bios = 0x81 disk = /dev/sdc bios = 0x82 disk = /dev/sda bios = 0x83 disk = /dev/sdb bios = 0x84 vga = normal read-only menu-scheme = Wg:kw:Wg:Wg lba32 prompt timeout = 50 message = /boot/message image = /boot/vmlinuz label = SuSE7.3 root = /dev/sda3 initrd = /boot/initrd optional image = /newdisk/vmlinuz label = RedHat7.3 root = /dev/sdc3 initrd = /newdisk/initrd-2.4.18-3.img optional other = /dev/hda1 label = Win2k image = /boot/memtest.bin label = memtest86 /////////////////////////////////////////////////////// Best regards, David List
On Sun, 2002-09-29 at 15:53, David List wrote:
I have just installed another disk, sdc, on my SuSE Linux 7.3 system. I have installed Red Hat 7.3 on it, since I need to test some software I am writing. I need to be *absolutely* sure it works with the libs that come with RH7.3.
After the RH7.3 installation, I restored my lilo, so that the system booted as before, and the RH7.3 installation was just lying there on sdc.
So, how do I make lilo understand the new situation? The new disk has been partitioned as follows: sdc1 /boot sdc2 swap sdc3 / I intend not to let the two installations "see" each other, but I temporarily mounted /dev/sdc1 on /newdisk and ran /sbin/lilo with the /etc/lilo.conf below. This didn't work. I can boot to SuSE 7.3, but when I try booting to RH7.3, I just see: Booting Red Hat 7.3......... and nothing more happens. Something must be wrong with my /etc/lilo.conf entry for the new installation, but what? Is it that just temporarily mounting the /dev/sdc1 and running /sbin/lilo won't work? My /etc/lilo.conf looks like this, now:
///////////////////////////////////////////////////////////////// append="hdc=ide-scsi noapic" boot=/dev/hda disk = /dev/hda bios = 0x80 disk = /dev/sr0 bios = 0x81 disk = /dev/sdc bios = 0x82 disk = /dev/sda bios = 0x83 disk = /dev/sdb bios = 0x84 vga = normal read-only menu-scheme = Wg:kw:Wg:Wg lba32 prompt timeout = 50 message = /boot/message
image = /boot/vmlinuz label = SuSE7.3 root = /dev/sda3 initrd = /boot/initrd optional
image = /newdisk/vmlinuz label = RedHat7.3 root = /dev/sdc3 initrd = /newdisk/initrd-2.4.18-3.img optional
other = /dev/hda1 label = Win2k
image = /boot/memtest.bin label = memtest86 ///////////////////////////////////////////////////////
Best regards, David List
When I had Slackware on another disk I simply followed what lilo did for Windows (setting for other = /dev/hda, might want to try /dev/sdc and then give it a label)...Only really works if RedHat has installed either lilo or grub onto your sdc...But this worked for me until I moved the 15gb drive onto my server for NWN... Just something to try... Matt
On Monday 30 September 2002 00:58, Matthew Johnson wrote:
When I had Slackware on another disk I simply followed what lilo did for Windows (setting for other = /dev/hda, might want to try /dev/sdc and then give it a label)...Only really works if RedHat has installed either lilo or grub onto your sdc...
Do you mean that making an 'other = /dev/sdc' entry would transfer control from the "original" lilo to the lilo installed on /dev/sdc, if I let Red Hat install it there? I didn't during the initial Red Hat installation, but I guess that could be changed still. Thank you for your answer. Best regards, David List
Suse 8.0 & Suse 7.1 I might be wrong but the boot process seems to look for the kernel in the default /boot. In my case I boot 7.1 & 8.0 on separate harddrives. To do this I copy the kernel from /boot on 7.1 to the boot partition on 8.0. Both kernels are in here. There is no problem accessing the files between the separate hard drives. They are just treated like any other file system. After compilining the RH kernel mount the Suse hd and copy it to /boot on Suse. Then boot into Suse and configure lilo. E.g boot = /dev/hda change-rules reset read-only menu-scheme = Wg:kw:Wg:Wg lba32 prompt timeout = 80 message = /boot/message image = /boot/vmlinuz label = linux root = /dev/hdb1 vga = 791 initrd = /boot/initrd # append = " hdd=ide-scsi" image = /boot/vmlinuz-2.4.17-ecs label = 40GB root = /dev/hdf3 ----------------------------snip In the above /boot/vmlinuz is Suse 8.0 and /boot/vmlinuz-2.4.17-ecs is Suse 7.1 The kernel vmlinuz-2.4.17-ecs resides in /boot on Suse 8.0 ----------------------------snip -rw-r--r-- 1 root root 963116 Jul 31 22:08 vmlinuz -rw-r--r-- 1 root root 886078 Jul 18 09:12 vmlinuz-2.4.17-ecs -rw-r--r-- 1 root root 83152 Mar 28 2002 vmlinuz.autoconf.h -rw-r--r-- 1 root root 40835 Mar 28 2002 vmlinuz.config -rw-r--r-- 1 root root 1035834 Mar 28 2002 vmlinuz.old -rw-r--r-- 1 root root 1035834 Jul 31 10:51 vmlinuz.suse -rw-r--r-- 1 root root 135 Mar 28 2002 vmlinuz.version.h I run lilo from Suse 8.0. Lilo will then give me two options at boot and the system can find both kernels ok. Brian Marr On Monday 30 September 2002 08:48, David List wrote:
On Monday 30 September 2002 00:58, Matthew Johnson wrote:
When I had Slackware on another disk I simply followed what lilo did for Windows (setting for other = /dev/hda, might want to try /dev/sdc and then give it a label)...Only really works if RedHat has installed either lilo or grub onto your sdc...
Do you mean that making an 'other = /dev/sdc' entry would transfer control from the "original" lilo to the lilo installed on /dev/sdc, if I let Red Hat install it there? I didn't during the initial Red Hat installation, but I guess that could be changed still.
Thank you for your answer.
Best regards, David List
participants (3)
-
Brian Marr -
David List -
Matthew Johnson