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.
Subj. As for me, my only complaint regarding Slackware is old stock kernel, it often can't work properly with new hardware, and manually updating it is a pain. Maybe Pat will invent some new mechanism for updating kernels?
I suspect Pat will update to 4.14 when it releases (assuming it's any good) given that it's the new LTS, but wouldn't expect any methodology changes if I were you. Updating kernels will likely be left to the sysadmin to do, much as before.
I agree with GazL. Stability is a major factor that Pat has to consider for all software going into Slackware as well as length of support. It is likely that Pat will continue to stick with LTS kernels, and now that the 4.4 and the 4.14 series kernels will have 6 years of support, it is likely they'll be used for any releases.
It is highly unlikely that Pat will move 14.2 beyond the 4.4 kernel. Any further updates to the kernel in 14.2 are highly likely to be within the 4.4 series. That is most likely to try to ensure the stability of the release, and he only updates it when there are serious security or implications, so don't expect more than a handful of updates. There have only been 6 updates from the 4.4.14 that 14.2 shipped with, and each were to patch a severe vulnerability that the previous version was affected by. Even now, Slackware 14.2 is at 4.4.88, which 4.4.93 is available from kernel.org.
Having Pat try and keep up with the kernel development releases for all of the Slackware versions that aren't EOL (6 different versions plus the constant updates in -current) seems unmanageable. If you need an newer kernel, it is relatively easy to do yourself.
That being said, if you don't mind others doing that work, forum member 55020 created his dusk project, which will compile newer versions of the kernels once they are available from kernel.org and he provides them as Slackware packages in a repo that is slackpkg+ compatible. He currently has packages for the 4.4, 4.12 (EOL), and 4.13 series kernels (he had a 4.9 series, but Pat was staying on top of those in -current, so it was a duplicated work). They work great in both stable and -current (I'm running his 4.13.7 kernel in my 14.1 machine).
lagavulin16 - have you tried compiling a kernel since version 4x came out? It is really easy and can have some great advantages besides just keeping up with new hardware. Take a look here --- Slack Kernel Building ---
You are right. They use to offer a bottle opener, but no more.
What I really want is a Slackware coffee mug. They are available elsewhere, but not from the "official" store.
The next release will require users to have the SlackwareŽ logo tattooed on their foreheads. Anyone not willing to do this can get to f ... f ... Fedora out of here!
It'll be ready sometime, and I'll expect it in the post.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.