https://bugzilla.novell.com/show_bug.cgi?id=784980 https://bugzilla.novell.com/show_bug.cgi?id=784980#c5 --- Comment #5 from Andrey Borzenkov <arvidjaar@gmail.com> 2012-10-17 02:55:28 UTC --- (In reply to comment #4)
# If the grub is the current loader, we'll handle the grub2 testing entry if [ "x${LOADER_TYPE}" = "xgrub" ]; then
Should not it really be x$LOADER_TYPE != xgrub2 -a x$LOADER_TYPE != grub2-efi? YaST2 still offers LILO and ELILO, and users may use them. Or are they completely unsupported now?
if [ -f /boot/grub/menu.lst ]; then
see above. Do you intentionally exclude (E)LILO?
# If grub config contains obsolete core.img path, remove and use the new one if /usr/bin/grep -l "^\s*kernel\s*.*/boot/%{name}/core.img" /boot/grub/menu.lst; then /sbin/update-bootloader --remove --image /boot/%{name}/core.img || true /sbin/update-bootloader --add --image /boot/%{name}/i386-pc/core.img --name "GNU GRUB 2" || true fi
# Install grub2 stuff and config to make the grub2 testing entry to work with updated version if /usr/bin/grep -l "^\s*kernel\s*.*/boot/%{name}/i386-pc/core.img" /boot/grub/menu.lst; then
So this means from now on GRUB2 will not be added to existing bootloader on update unless it was already present from earlier attempts. Is it intentional? -- 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.