On 2014-07-23 00:55 (GMT-0500) David C. Rankin composed:

As part of https://bugzilla.novell.com/show_bug.cgi?id=887629 we need to install and test the latest kernel:stable kernel. Adding the repo in yast and checking, it does not show the -devel files to know that I am getting the same kernel setup I have with the kernel from 13.1/update. Also, I do *NOT* want to replace my current kernel, I simply want to install in-addition-to the current kernel. multiversion is set to include kernel in zypp.conf.

If you're truly worried about losing an installed kernel, set a lock: zypper al kernel*. To add another without first removing the lock, specify the particular one you want installed as input to zypper -v in and answer yes to the 1st options question provided (proceed to install, ignore lock).

That brings me to the real issue. In yast sw-management, when I select update for the various kernel packages, how can I confirm that it will install and leave the current kernel? Just rely on the multiverion setting, cross-fingers and pray?

If you just let the system work with default multiversion settings, nothing should be removed until you have 3 installed and a 4th becomes available that you allow yast or zypper to install. No finger crossing should be necessary.

Would it just be better to install with 'rpm -ivh *.rpm' in a directory with the updated kernel packages? This seems like the simplest way.

I think not.

My current kernel packages are:

kernel-default-devel-3.11.10-17.2.x86_64.rpm kernel-desktop-3.11.10-17.2.x86_64.rpm kernel-desktop-devel-3.11.10-17.2.x86_64.rpm kernel-devel-3.11.10-17.2.noarch.rpm kernel-firmware-20130714git-2.17.1.noarch.rpm kernel-source-3.11.10-17.2.noarch.rpm kernel-syms-3.11.10-17.1.x86_64.rpm kernel-xen-devel-3.11.10-17.2.x86_64.rpm mkinitrd-2.8.1-2.1.x86_64.rpm ucode-amd-20130714git-2.17.1.noarch.rpm

Are there any packages I'm missing?

http://lists.opensuse.org/opensuse-kernel/2014-06/msg00089.html

I'll wait on the braintrust to make sure I don't install into a problem, but my plan would be to download the same packages from kernel:stable and install with rpm -ivh and presume zypp.conf multiversion would preserve my existing kernel, and grub2 menu generation would take place automagically making the new kernel available as it did with grub.

Solid plan?

All my 13.1 systems use original multiversion settings shipped in zypp.conf. On most of them, I'm removing extra kernels (zypper -v rm) before the system can get any round tuits for any removals, so that I have only running kernel after the manual removal I do before letting a new one install. By "letting" what I do is set/unset a lock "kernel*", which means in most cases everything else gets upgraded before I permit the kernel to upgrade. I'm pretty sure I have Jiri's 3.12.x running on all my 13.1 insallations, but there could be one I've forgotten about still running latest 13.1 updates kernel. In summary, on most of my 13.1 installation at the end of any updates session I have a freshly installed kernel plus the last kernel previously installed, but I can change that by removing the newest if I want before installing the latest available, so what I have when done will be latest and 2nd previous. The reason for keeping 2 instead of 3, without making any changes to zypp.conf, is to avoid some time wasting caused by https://bugzilla.novell.com/show_bug.cgi?id=881780 a dracut bug in Factory matching mkinitrd behavior in 13.1. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org