Am Dienstag, den 27.10.2009, 23:23 -0400 schrieb Chris Jones:
> While detecting other kernels, update-grub generates the following:
>
> menuentry "Debian GNU/Linux, kernel 2.6.24-etchnhalf.1-686 (on /dev/sda12)" {
>
> insmod ext2
>
> set root=(hd0,12)
>
> search --no-floppy --fs-uuid --set
> 042b6b67-5464-426e-a60a-21b71dfbcb74
> linux /boot/vmlinuz-2.6.24-etchnhalf.1-686 root=/dev/hda5 ro
>
> initrd /boot/initrd.img-2.6.24-etchnhalf.1-686
>
> }
>
> menuentry "Debian GNU/Linux, kernel 2.6.24-etchnhalf.1-686 (single-user mode)
> (on /dev/sda12)" {
> insmod ext2
>
> set root=(hd0,12)
>
> search --no-floppy --fs-uuid --set
> 042b6b67-5464-426e-a60a-21b71dfbcb74
> linux /boot/vmlinuz-2.6.24-etchnhalf.1-686 root=/dev/hda5 ro single
>
> initrd /boot/initrd.img-2.6.24-etchnhalf.1-686
>
> }
>
>
> /dev/sda12 is the correct partition, which is correctly reported in the
> menuentry and set root= statements, but not on the linux statement.
>
> The result, when trying to boot these entries, is that another system
> which has its /root & /root/boot on /dev/sda5 is booted instead.
>
> This happens with grub 1.97 as shipped by ubuntu 9.10.
>
> Not sure this qualifies as a bug, or just incorrect setup my end.
>
os-prober is a seperate package. It has nothing to do with us, except
that we call it to generate menuentries, if it's avaible.
It takes the root= value for the Linux kernel out of lilo.conf, menu.lst
or grub.cfg depending what you have on that partition installed.
So you have to change the bootloader configuration of your Debian etch.
--
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
