https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #52 from Ulrich.Windl@rz.uni-regensburg.de 2007-03-27 07:29 MST ------- I haven't looked into the postinstall scripts, but the problem seems to be this: The kernel upgrade should be totally independent of boot or module tools, that is it should not contain its own tools. Now there's nothing wrong with the current kernel, but just the way /boot/grub/menu.lst is modified. If some boot tool were broken, we could simply update that, and not the kernel. OK, I looked into the RPM and found: # handle 10.2 and SLES10 SP1 if [ -x /usr/lib/bootloader/bootloader_entry ]; then /usr/lib/bootloader/bootloader_entry \ add \ default \ 2.6.18.8-0.1-default \ vmlinuz-2.6.18.8-0.1-default \ initrd-2.6.18.8-0.1-default [...] When there is in /boot: initrd -> initrd-2.6.18.8-0.1-default vmlinuz -> vmlinuz-2.6.18.8-0.1-default and in menu.lst: title openSUSE 10.2 root (hd0,0) kernel /vmlinuz root=/dev/system/root resume=/dev/hda2 initrd /initrd Is there any necessity for a new default boot entry? Also note that the online update did not leave the previous kernel around, so any additional boot entry for a previous kernel would not help a bit in case the current kernel fails. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.