On Wed April 30 2003 2:56 am, Richard Bos wrote:
Op woensdag 30 april 2003 03:08, schreef Stan Glasoe:
On Tue April 29 2003 5:01 pm, Yongtao Yang wrote:
Richard Bos <radoeka@xs4all.nl> writes:
# Modified by YaST2. Last modification on Tue Apr 29 21:11:45 2003
title linux kernel (hd1,4)/vmlinuz root=/dev/hdb7 hdc=ide-scsi vga=791 initrd (hd1,4)/initrd
...
title suse kernel (hd1,4)/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791
^^^^^， Here, I am a little surprised, why did you share the same kernel? Is it just a typo?
initrd (hd1,7)/initrd
-- Yongtao Yang
email: yongtao.yang@telia.com
You should change the "kernel (hd1,4)" to "kernel (hd1,7)", without the quotes of course, to match the root=/dev/hdb8 and initrd (hd1,7).
title suse kernel (hd1,7)/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791 initrd (hd1,7)/initrd
Changed that as well, but that did not help either.
Should it theoretically work if the the config file is as follows?
.... title linux kernel (hd1,4)/vmlinuz root=/dev/hdb7 hdc=ide-scsi vga=791 initrd (hd1,4)/initrd
title suse kernel (hd1,7)/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791 initrd (hd1,7)/initrd .....
Yast made it without the "hdc=ide-scsi vga=791" and the initrd line. for "suse".
-- Richard Bos Without a home the journey is endless
In my theory, no, it shouldn't work. My /boot/grub/menu.lst has absolute path names. Specifying /vmlinuz looks to be a relative path and AFAIK grub don't do relative paths. Change these relative paths to absolutes. On my system I've quit using a separate /boot partition and leave it as a directory off /. My grub then has /boot/vmlinuz and /boot/initrd after the drive/partition designations. Change yours as follows and see what happens. The root=/dev/hd?? is OK. title linux kernel (hd1,4)/boot/vmlinuz root=/dev/hdb7 hdc=ide-scsi vga=791 initrd (hd1,4)/boot/initrd title suse kernel (hd1,7)/boot/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791 initrd (hd1,7)/boot/initrd