Feature changed by: Lars Müller (lmuelle) Feature #310856, revision 6 Title: don't remove custom grub entries openSUSE-11.4: Unconfirmed Priority Requester: Mandatory Requested by: Christian Boltz (cboltz) Partner organization: openSUSE.org Description: from https://bugzilla.novell.com/show_bug.cgi?id=648565 (written by Nico Gruber): Applying a kernel update will delete custom grub entries with this kernel and add a default one Steps to Reproduce: 1) duplicate a grub entry and add some parameter to the kernel command line 2) update kernel, e.g. by doing auto-update with one of the provided kernel updates Actual Results: the created custom entry in grub which uses the outdated kernel which has now been updated is removed, a default entry is created, e.g. "Desktop -- openSUSE 11.3 - 2.6.34.7-0.4" Expected Results: all (custom) entries with the updated kernel should be changed in order to boot the new one - without changing either the name of the entry, nor any parameters Custom entries can be there for various reasons, and I need them on nearly every system I use (see "use cases"). Please change perl-bootloader as described in "Expected Results" above. It should not remove or change any entry in menu.lst, except filename changes of kernel and initrd at a kernel update. Relations: - Bug report (novell/bugzilla/id: 648565 ) https://bugzilla.novell.com/show_bug.cgi?id=648565 Use Case: * Servers with RAID: fallback entry to boot from the second disk * abusing ;-) a boot parameter like x11failsave to switch between two xorg.conf files without hacking the initscript Business case (Partner benefit): openSUSE.org: Because custom bootloader entries are used quite often, and it's very annoying if you have to re-add them at every kernel update. + Discussion: + #1: Lars Müller (lmuelle) (2010-11-28 17:05:55) + Why not enableing the currently unlimited multiversion feature in + /etc/zypp/zypp.conf ? + Doesn't that already cover the issue? -- openSUSE Feature: https://features.opensuse.org/310856