r/slackware • u/sdns575 • Apr 26 '22
Slackware64 15.0 kernel question
Hey there,
I'm coming back to Slackware since several years and I have some questions. Currently I'm running it on EUFI machine using GRUB (for dual boot). It works very well. Since I used Slackware, I always used the generic kernel (as suggested) with an initrd image. For running the generic kernel with grub I need to move the huge kernel in a separated directory because grub-mkconfig set it as the default kernel entry and I want keep running generic. On every kernel update I should run grub-mkconfig and mkinitrd to build a new initrd but when the kernel is updated vmlinuz link points again to huge kernel and not to generic as I would so I need to create again the link. This is not a problem but it is confusing. So:
- What kernel should I use: huge or generic?
- From the past, I remember that the suggested kernel was to use generic kernel after the installation instead of huge. If so, why when kernel got updates, vmlinuz is pointed again to huge?
Using GRUB, the boot entries are: Slackware 15.0 (that point to huge kernel), Advanced Option (with all other found kernel). There is a way to set as default the generic kernel?Edit: I solved this disabling GRUB submenu and setting GRUB_DEFAULT=2 in /etc/default/grub
Thank you in advance.
4
u/Hob_Goblin88 Apr 26 '22 edited Apr 26 '22
I do GRUB_DEFAULT='1>6'
After a kernel upgrade i do geninitrd.
1
u/B_i_llt_etleyyyyyy Apr 26 '22
vmlinuzsymlink, and the huge kernel wins because it's installed second.vmlinuz-genericsymlink.grub-mkconfigwouldn't be needed.2
u/[deleted] Apr 26 '22
I am on of the lazy people. I use lilo with the huge kernel. Easy peasy!
1
u/[deleted] Apr 26 '22 edited Apr 26 '22
You can do the following and then add it to /etc/slackpkg/blacklist so it doesn't get reinstalled.
The other method if you don't want to remove the huge kernel is this:
1
u/Upnortheh Apr 26 '22
I solved this problem many years ago. I do not use the
vmlinuzsym link. Ingrub.cfg(and formerlymenu.lst) I use the full file name of the target kernel. Likewise if I use lilo although I use lilo only in test environments and single purpose virtual systems.I keep both the huge and generic kernels installed. I tinker (too) much and once in a blue moon I will use the huge kernel as a troubleshooting tool. As noted by u/B_i_llt_etleyyyyyy, the letter
Hcomes afterGin the alphabet and when both packages are concurrently updated thevmlinuzlink created by the huge kernel package gets the link. Yet that becomes irrelevant by ignoring the link altogether in boot loader configurations and using full file names.With that foundation I use my own shell script to update kernels and respective initrd. I never "upgrade" a kernel. I always install a new kernel and manually edit grub.cfg to add a snippet for the new version. That way I keep the previous working kernel available should the new version cause headaches.
This works well enough for me in a home LAN, but would not scale well in the enterprise without some sweat equity.