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.
Considering the last wireguard-linux-compat (module) was tagged 20201221, and 5.9.16 was released on 2020-12-21, I'd say you arent missing out on anything for now.
? Slint that I maintain currently ships linux 5.4.75 (compiled with a genuine gcc 5.5 from Slackware 14.2), with no issue so far and no user complaint. I consider upgrading to 5.10.n when dust will have settled a bit.
Slackware has never had a kernel release updated beyond the the patches for the kernel release included in that Slackware stable release. While it wouldn't actually require rebuilding things against the new headers, if 14.2 saw a 5.4 or 5.10 release, it just wouldn't be the same Slackware that we've used over the years (maybe it'll be a newer, better Slackware, but I prefer the stability of the same kernel provided by Pat and upgrading my own if I feel the need is there for my system).
Slackware has never had a kernel release updated beyond the the patches for the kernel release included in that Slackware stable release. While it wouldn't actually require rebuilding things against the new headers, if 14.2 saw a 5.4 or 5.10 release, it just wouldn't be the same Slackware that we've used over the years (maybe it'll be a newer, better Slackware, but I prefer the stability of the same kernel provided by Pat and upgrading my own if I feel the need is there for my system).
Answering to post #2908 the way I did was just to provide an evidence that rebuilding against the new headers in the use case mentioned in this post was not necessary. I have no intend to tell Slackware users how they should use and possibly customize their system and I firmly believe that Patrick doesn't either. Maybe I didn't get the message conveyed by your answer?
PS Indeed using a customized kernel leads to run a "not completely genuine" Slackware, but in my opinion this is only useful to know when providing support for this system if that can cause an issue. Whether the kernel branch should be upgraded in Slackware 14.2 without changing the Slackware version number is a decision up to Patrick.
Last edited by Didier Spaier; 01-04-2021 at 01:35 AM.
Reason: PS added.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,153
Original Poster
Rep:
Year 2021, Round 1.
Another batch of updates has been scheduled for release on Wednesday, 06 January 2021, at approximately 16:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Tuesday (depending on your time zone).
Answering to post #2908 the way I did was just to provide an evidence that rebuilding against the new headers in the use case mentioned in this post was not necessary. I have no intend to tell Slackware users how they should use and possibly customize their system and I firmly believe that Patrick doesn't either. Maybe I didn't get the message conveyed by your answer?
PS Indeed using a customized kernel leads to run a "not completely genuine" Slackware, but in my opinion this is only useful to know when providing support for this system if that can cause an issue. Whether the kernel branch should be upgraded in Slackware 14.2 without changing the Slackware version number is a decision up to Patrick.
I initially had only read the beginning part of their post, saying that it wouldn't be Slackware anymore. I somehow missed the last part until I had finished typing up most of my reply. Rather than just delete the whole thing, I modified it a bit and posted it, but I probably should've added a bit more to it.
My Acer laptop (AMD/ATI/Radeon) was blocked by kernel 5.10.2 an 5.10.4, so I downgraded to a built 5.4.86 version.
It's ok now and I'll keep this version for next update
5.11-rc2 sed: can't read modules.order: No such file or directory Makefile:1420: recipe for target '_modinst_' failed make: *** [_modinst_] Error 2
I've seen errors like these that are usually resolved on the next release, but this seems to be just me. Happened both from patching and from downloading the tarball.
5.11-rc2 sed: can't read modules.order: No such file or directory Makefile:1420: recipe for target '_modinst_' failed make: *** [_modinst_] Error 2
I've seen errors like these that are usually resolved on the next release, but this seems to be just me. Happened both from patching and from downloading the tarball.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
