[SOLVED] Slackware64-15.0 (stable): Which first? upgrade-all, new kernel or patch for aaa-base?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Now I am once again paralyzed by not knowing in which order to proceed, I have seen very many scenarios, but none that fit my specific situation, so I don't have a clear understanding of how to proceed.
Shall I install the 5.15.38 kernels before I apply the patches? - it will be my first time applying patches. And must I apply the aaa-base patch before running "slackpkg uppgrade-all" ?
I have made a back-up of the boot folder in another partition -this is a multiboot machine booted by grub in another distro - in case it goes wrong with 5.15.38 but I would like to learn how to proceed with applying the patches when blacklisting present kernel (5.15.27).
It is here I am unsure if the patches will be better applied under the new kernel or under the present kernel. I can not decide what it means that among the patches there is one for the 5.15.38 kernel. Does it mean the new kernel is critical for a successful application of the other patches? Or are the other patches critical to the installation or patching up to the new kernel?
It doesn't matter. When you run "slackpkg upgrade all" as long as you didn't blacklist them the kernel packages will be in the list up available updates. Just install all the updates and kernel will automatically be upgraded for you. I prefer to do my kernel updates manually, but you said you were interested in the slackpkg way. Just be sure after the packages are installed you make a new initrd and update your bootloader.
Another thing you don't have to do but I recommend, is keep the original kernel modules package installed that shipped with the 15.0 which is 5.5.19 along side the new kernel modules package. If you ever need to use the Slackware ISO as a rescue disc it will make your life easier if you have those modules. but again this is not necessary.
Another thing you don't have to do but I recommend, is keep the original kernel modules package installed that shipped with the 15.0 which is 5.5.19 along side the new kernel modules package. If you ever need to use the Slackware ISO as a rescue disc it will make your life easier if you have those modules. but again this is not necessary.
AFAIR upgrading kernel modules automatically deletes the old set. That's why I don't do it. I prefer to install the new module tree alongside the old one, then remove the old modules afterwards.
AFAIR upgrading kernel modules automatically deletes the old set. That's why I don't do it. I prefer to install the new module tree alongside the old one, then remove the old modules afterwards.
That's why I blacklist the kernel and its modules, so that slackpkg leaves them alone. I use 'installpkg' to install the new kernel plus its modules, manually update (e)lilo and always ensure that the currently successfully running kernel remains one of the boot selections in (e)lilo.
Code:
# Automated upgrade of kernel packages may not be wanted in some situations;
# uncomment the lines below if that fits your circumstances, but note that
# kernel-headers should *not* be blacklisted:
#
kernel-generic.*
#kernel-huge.*
kernel-modules.*
#kernel-source
daedra wrote:
It doesn't matter. When you run "slackpkg upgrade all" as long as you didn't blacklist them the kernel packages will be in the list up available updates. Just install all the updates and kernel will automatically be upgraded for you. I prefer to do my kernel updates manually, but you said you were interested in the slackpkg way. Just be sure after the packages are installed you make a new initrd and update your bootloader.
Thanks for your perfectly clear answer. But I want to be able to boot my old kernel in case something goes wrong and the new one does not. What would you suggest to that end ? And would it matter, in your scenario, when - before or after uppgrade-all I install the new kernel firmware ?
hazel wrote:
AFAIR upgrading kernel modules automatically deletes the old set. That's why I don't do it. I prefer to install the new module tree alongside the old one, then remove the old modules afterwards.
windu wrote:
That's why I blacklist the kernel and its modules, so that slackpkg leaves them alone. I use 'installpkg' to install the new kernel plus its modules, manually update (e)lilo and always ensure that the currently successfully running kernel remains one of the boot selections in (e)lilo.
Code:
# Automated upgrade of kernel packages may not be wanted in some situations;
# uncomment the lines below if that fits your circumstances, but note that
# kernel-headers should *not* be blacklisted:
#
kernel-generic.*
#kernel-huge.*
kernel-modules.*
#kernel-source
Thank you windu! I think this is the way I want to go, which hazel has also pointed out. Does it matter when the new kernel is installed? Firmware ? aaa-base?
AFAIR upgrading kernel modules automatically deletes the old set. That's why I don't do it. I prefer to install the new module tree alongside the old one, then remove the old modules afterwards.
Yes that is true. that is why I do my kernel upgrades manually, but the OP said he wanted to use slackpkg.
Thank you windu! I think this is the way I want to go, which hazel has also pointed out. Does it matter when the new kernel is installed? Firmware ? aaa-base?
That is a smart way to go. Keeping your old kernel as a fail safe in case the new kernel doesn't boot is always a good idea. And no it will not matter what order you take, kernel first then patches, patches then kernel, either way it will work. Just make sure blacklist the kernel packages or don't select them when you run slackpkg. After the patches are updated you can grab the new kernel packages like this if you don't already have them.
Thanks once more hazel! I got it! In your scenario when do you install the new kernel? Before or after the upgrade-all? Firmware and aaa-base, can I just forget about them ?
Surprisingly it doesn't much matter when you update the kernel. It runs more or less independently of all the other software. In fact you can install any kernel within reason and it will work. I update userland first (with the kernel and its modules blacklisted), then do the kernel afterwards at leisure.
You only need kernel firmware if you have hardware that requires extra drivers. Mostly that's certain wifi cards.
aaa_base: this one is just directories, nearly all of which you have already. But there are a couple of configuration files included, so you should update this if it's up for it. It won't clash with anything else, that's for sure.
@daedra: that lftp command is cool. I must admit I do it the easy way and download the kernel and modules using firefox.
Another thing you don't have to do but I recommend, is keep the original kernel modules package installed that shipped with the 15.0 which is 5.5.19 along side the new kernel modules package. If you ever need to use the Slackware ISO as a rescue disc it will make your life easier if you have those modules. but again this is not necessary.
As well as having a "Backup" line in /etc/lilo.conf with this kernel. Just a recommendation for 15.0, "must have" for -current
It might be risky, and I might come unstuck some time, but I've used slackpkg to update/upgrade all the kernel changes we had in 14.2, current for the months I ran it, and now 15.0.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.