[zypp-devel] zypp.conf multiversion kernel config -- different retention for different kernels?
I have a server I use as a Xen host. On occassion, I need to boot into !Xen, kernel-default. I want to keep multiple kernel-xen versions installed, but only one (eventually 2), kernel-default. Following Chapter 12. Installing Multiple Kernel Versions https://activedoc.opensuse.org/book/opensuse-system-analysis-and-tuning-guid... I've edited zypp.conf multiversion = kernel-xen multiversion.kernels = latest,latest-1,running,3.16.7-7,3.19.4-1.g74c332b and rebooted. With that config, I'd expected that I'd end up with ONE kernel-default, and several kernel-xen. Instead, I find rpm -qa | grep -i ^kernel kernel-default-4.0.0-1.1.g49e42b3.x86_64 kernel-default-3.19.4-1.1.g74c332b.x86_64 kernel-default-3.16.7-7.1.x86_64 kernel-xen-4.0.0-1.1.g49e42b3.x86_64 kernel-xen-3.19.4-1.1.g74c332b.x86_64 kernel-firmware-20150209git-36.1.noarch I.e., multiple kernel-default, and kernel-xen-3.16.7-7.1.x86_64 which existed before the edit/reboot, is now gone. What's the right multiversion config to do what I need? LT -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org To contact the owner, e-mail: zypp-devel+owner@opensuse.org
On Wednesday 22 April 2015 17:36:35 lyndat3@your-mail.com wrote:
I've edited zypp.conf
multiversion = kernel-xen multiversion.kernels = latest,latest-1,running,3.16.7-7,3.19.4-1.g74c332b
and rebooted.
With that config, I'd expected that I'd end up with ONE kernel-default, and several kernel-xen.
multiversion= defines how NEW packages are going to be INSTALLED. 'Normal' packages like 'rpm -U', automatically obsoleting old versions of the package. 'Multiversion' packages like 'rpm -i' are just added. Changing the setting does not affect already installed packages. Your kernel-default packages will stay until the next kernel-default package is (re-)installed without multiversion ('rpm -U'). E.g. zypper in -f kernel-default-4.0.0-1.1.g49e42b3 multiversion.kernels= is actually an option of the purge-kernels service from package mkinitrd. They simply hijacked the libzypp config file. I don't know in detail how purge-kernels works, so I'm not sure whether it actually evaluates zypps multiversion= settings. It may verry well be it simply looks at the installed kernels and makes it's decision based on the config values. That's probably why the multiple 'kernel-default' are kept. But I also can't explain why kernel-xen-3.16.7 is gone. For an explanation/bugfix please file a bugreport at bugzilla.opensuse.org for package mkinitrd. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres SUSE LINUX GmbH, Development, ma@suse.de Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 74 053-0 +------------------------------------------------------------------+ SUSE Linux GmbH GF: Felix Imendörffer, Jane Smithard, Jennifer Guild Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org To contact the owner, e-mail: zypp-devel+owner@opensuse.org
On Thu, Apr 23, 2015, at 02:44 AM, Michael Andres wrote:
multiversion= defines how NEW packages are going to be INSTALLED. 'Normal' packages like 'rpm -U', automatically obsoleting old versions of the package. 'Multiversion' packages like 'rpm -i' are just added.
Changing the setting does not affect already installed packages. Your kernel-default packages will stay until the next kernel-default package is (re-)installed without multiversion ('rpm -U'). E.g.
zypper in -f kernel-default-4.0.0-1.1.g49e42b3
You're correct -- next update/upgrade forced the changes.
multiversion.kernels= is actually an option of the purge-kernels service from package mkinitrd. They simply hijacked the libzypp config file.
I don't know in detail how purge-kernels works, so I'm not sure whether it actually evaluates zypps multiversion= settings. It may verry well be it simply looks at the installed kernels and makes it's decision based on the config values.
That's probably why the multiple 'kernel-default' are kept. But I also can't explain why kernel-xen-3.16.7 is gone.
For an explanation/bugfix please file a bugreport at bugzilla.opensuse.org for package mkinitrd.
Still not clear why the 3.16.x kernel-xen vanished. Will explore that. Since we have both multiversion multiversion.kernels in zypp.conf, how can you keep different #'s of different kernel flavors? E.g., for kernel-xen, keep latest,latest-1,running,3.16.7-7,3.19.4-1.g74c332b but for kernel-default, only keep latest,running,3.16.7-7 ? It's clear how to keep all the same versions for different flavors, but not different #'s for different kernels. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org To contact the owner, e-mail: zypp-devel+owner@opensuse.org
On Sunday 26 April 2015 19:13:16 lyndat3@your-mail.com wrote:
Since we have both
multiversion multiversion.kernels
in zypp.conf, how can you keep different #'s of different kernel flavors?
AFAIK mkinitrd does not support this. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres SUSE LINUX GmbH, Development, ma@suse.de Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 74 053-0 +------------------------------------------------------------------+ SUSE Linux GmbH GF: Felix Imendörffer, Jane Smithard, Jennifer Guild Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org To contact the owner, e-mail: zypp-devel+owner@opensuse.org
participants (2)
-
lyndat3＠your-mail.com -
Michael Andres