On 18/07/17 20:59, Carlos E. R. wrote:
On 2017-07-18 05:26, Basil Chupin wrote:
Hi John,
I'll add a bit more to what I stated above re doing something so as not to clobber the 4.11 or 4.12 kernel from /repo/Kernel:/stable....
If you are using zypper to update your oS or even use Yast itself, both or either will try and re-install the original installed kernel ie, 4.4.x because in all probability it is marked as being installed in Yast's Version information. You will see what I mean if you:
* start Yast * search for 'kernel' and you will see a number of entries with 'kernel' in them * highlight each one (by clicking on each one) and then select VERSION * you may see that kernel 4.4.x is still ticked as being installed even though 4.11/4.12 is also shown as installed
and this last item is what will make zypper or Yast try an re-install 4.4.x kernel. Nevertheless, grub will boot the most recent kernel by default, no matter if the original is still installed.
Umm, not necessarily... But you may absolutely correct in what you say. Let me explain... I experienced just the opposite to what you wrote above only yesterday (and before I wrote the above 'addendum to the addendum'). Perhaps something did not happen which I expected and therefore what happened did happen :-). After installing the new 4.12.x kernel, I looked in /boot and found that the '@vmlinuz' and @initrd' both pointed to the old (4.4.x) kernel. Now this may have resulted from some part of the kernel family of files not being installed during the many attempts I had to go thru while trying to stop Yast from re-installing 4.4.x :-). I guess the point here is to check in /boot as to which kernel is actually configured for use at boot time before hitting the 'reboot' "button" :-). BC -- You are NOT entitled to your opinion. You are entitled to your INFORMED opinion. Nobody is entitled to be ignorant. Harlan Ellison -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org