Kernel updates removes user choices from /boot/grub/menu.lst
When doing a kernel patch or update (as in eg zypper dup), the upgrade process re-writes the menu.lst entries for the kernel parameters with the default string from /etc/sysconfig/boot-something.conf
Not a lot of end-users are aware of that file (in my case it took 5 years to realise what was happening), and are instead constantly having to re-write missing kernel paraemters into the menu.lst file.
For instance, most sane folks would use splash=verbose as opposed to splash=silent, and for anyone using console=, brokendriver=, etc this is quite disasterous in the case of remote systems that suddenly become unreponsive / unreachable as a result of the kernel upgrade changing very important parameters.
Instead of taking the default from an obscure config file that no other distro even uses, I'd suggest that the kernel param line is taken as-is from the menu.lst / elilo.conf files, not set to some static value.
Because I have spent hours trying to recover remote systems where I lost the console=ttyS0 serial console and a brokendriver= clause that caused the remote systems in question to fail to boot following a simple kernel patch.
Set user benefit
You can add different relations here, for example duplicate features, obs projects, urls...
To embedd an image you can simply upload it to paste.opensuse.org and add a relation to its raw url.
Set release notes
Wanting to preserve eg
across kernel updtaes
Last change: 5 years ago