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.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,166
Original Poster
Rep:
FWIW, the second time around 5.12-rc7 built without errors.
The first attempt was at the prompt (out of X) while running the 5.11.12 kernel.
The second attempt was inside a terminal, while in X, and running 5.12-rc6.
Regardless, so far, everything I do with the computer works as it should with 5.12-rc7.
Last edited by cwizardone; 04-12-2021 at 08:43 AM.
Reason: Typo.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,166
Original Poster
Rep:
Year 2021, Round 26.
Another batch of updates has been scheduled for release on Wednesday, 14 April 2021, at approximately 08:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Tuesday (depending on your time zone).
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564
Rep:
when will we have the capability of upgrading the kernel without rebooting?
With that "never ending" story every two or three days, the uptime isn't very high.
when will we have the capability of upgrading the kernel without rebooting?
With that "never ending" story every two or three days, the uptime isn't very high.
I'm serious when I say this.
BUT, is not as simple as you think.
I seen (at a Linux conference) a presentation of methods of upgrading kernels on-fly, and it's basically about a kexec execution followed by a hot reboot, for taking over.
It minimize the down-time on a server, BUT it still counts as a reboot.
So, your uptime would not be saved, but reboot time would be considerable shorten.
Last edited by LuckyCyborg; 04-13-2021 at 11:37 AM.
Ksplice and Kpatch of Linux kernels are about patching on-fly the things.
I do not known well about Ksplice thing, but the kernel patches are basically some kernel modules which are loaded, well... on-fly.
However, this is not an effective kernel upgrade, but more about fixing things on emergency, until a proper reboot is done and a superior version starts.
when will we have the capability of upgrading the kernel without rebooting?
With that "never ending" story every two or three days, the uptime isn't very high.
I'm serious when I say this.
Unless you have unsupported hardware there is no requirement to regularly upgrade your kernel. You can blacklist it and commented out entries are already there I suppose because it is so common to blacklist kernel updates.
I simply build an even newer kernel and stick with it for a long time. This box running several instances of Current is using 5.11.11. One of the installs will probably try 5.12.1 when it is released.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.