On 17/08/2019 04:01, zb4ng wrote:
Auto-Update is active and the new kernel really is installed:
~\:09:59:26 > ls -l /boot | grep vmlinuz lrwxrwxrwx 1 root root 35 16. Aug 20:23 vmlinuz -> vmlinuz-4.12.14-lp151.28.13-default -rw-r--r-- 1 root root 7331952 15. Mai 02:26 vmlinuz-4.12.14-lp151.27-default -rw-r--r-- 1 root root 7340144 15. Jul 13:25 vmlinuz-4.12.14-lp151.28.10-default -rw-r--r-- 1 root root 7344240 11. Aug 10:54 vmlinuz-4.12.14-lp151.28.13-default ~\:09:59:26 >
new kernel? On a 15.x? I'm running cat /etc/os-release NAME="openSUSE Leap" VERSION="42.3" and I haven't updated my kernel for over a week now uname -a Linux main.HOME.SystemI.ca 5.2.8-2.ga44175e-default #1 SMP Mon Aug 12 07:11:56 UTC 2019 (a44175e) x86_64 x86_64 x86_64 GNU/Linux Now I'm sure that 4.x can be patched patched patched to look like 5.x, but why? For the effort of 'update' automation, and keeping a few back versions around for the if-but-maybe and testing. # zypper lr --uri| grep -i kernel 13 | Kernel_Stable | Kernel_Stable | Yes | (r ) Yes | Yes | http://download.opensuse.org/repositories/Kernel:/stable/standard/
I figured, I should let grub refresh its boot entries, so I started the boot configuration in Yast on 15.0, but had no success with it.
NoNoNoNo. Grub doesn't refresh, it's taken care of by zypper when the update runs. KISS.
Maybe, i could simply delete the old kernels manually? But how can i avoid this from happening every time a new patch is released?
NoNoNoNo. It's taken care of by zypper. In the file /etc/zypp/zypp.conf you can control this (along with many other things: the comments in the file are worth reading thoroughly!) ## Comma separated list of kernel packages to keep installed in parallel, if the ## above multiversion variable is set. Packages can be specified as ## 2.6.32.12-0.7 - Exact version to keep ## latest - Keep kernel with the highest version number ## latest-N - Keep kernel with the Nth highest version number ## running - Keep the running kernel ## oldest - Keep kernel with the lowest version number (the GA kernel) ## oldest+N - Keep kernel with the Nth lowest version number ## ## Note: This entry is not evaluated by libzypp, but by the ## purge-kernels service (via /sbin/purge-kernels). ## ## Default: Do not delete any kernels if multiversion = provides:multiversion(kernel) is set multiversion.kernels = latest,latest-2,latest-1,running #==== THIS IS MY SETTING Yes, you can accumulate kernels until you explicitly purge them! # ls /boot/vmlinux* /boot/vmlinux-5.2.1-2.gbf5c01b-default.gz /boot/vmlinux-5.2.6-1.g187170c-default.gz /boot/vmlinux-5.2.2-2.gadfddac-default.gz /boot/vmlinux-5.2.7-2.geaa06bb-default.gz /boot/vmlinux-5.2.2-3.gafc4698-default.gz /boot/vmlinux-5.2.8-1.gbf37e83-default.gz /boot/vmlinux-5.2.3-1.gf5296b5-default.gz /boot/vmlinux-5.2.8-2.ga44175e-default.gz /boot/vmlinux-5.2.4-1.g5034dba-default.gz # purge-kernels Removed: kernel-default-5.2.1-2.1.gbf5c01b.x86_64 kernel-default-5.2.2-2.1.gadfddac.x86_64 kernel-default-5.2.2-3.1.gafc4698.x86_64 kernel-default-5.2.3-1.1.gf5296b5.x86_64 kernel-default-5.2.4-1.1.g5034dba.x86_64 kernel-default-5.2.6-1.1.g187170c.x86_64 OH MY! Look at all the space reclaimed under /lib! So what's the point of using zypper? Many things. it maintains a database of the updates, patches, for one thing. But you can think of it as a collection of smart scripts for doing updates. There's a lot of low-level details, such as getting grub updated that you mention, and the parametrized building of the kernel load image with the boot blocks and drivers that you want/need via Dracut. As has been mentioned here before, you can strip down the initrd to have just what you want for a faster boot. Yes, you COULD do all this, all these parts, separately, manually, making notes of the dates and patches in your little black book rather than the zypper database. Yes, you could have a check-list to make sure you did each step in the correct sequence with the long list of arguments on the command line in the right order with the right spelling. Think of it as a "learning experience" and after the third time you make a mistake and brick your system you might decide to run zypper instead. BTDT. Now, in order to keep what little grey hair I still have I'm working on learning from the experiences of others rather than acquiring 'wisdom' the hard way. Youthful arrogance and independence is great for the young and in circumstances where there is the 'slack' to allow you to learn from the mistakes. Personally I think scripts and automation and well documented config files are wonderful. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org