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.
According to Greg Kroah-Hatman document, the Slackware stable kernel politics is not the best. The Slackaware stable (14.2) would go including all the kernels in the 4.4 branch (the last is 4.4.152, and the last kernel in Slackare 14.2 is 4.4.144).
Um no, that is not what Greg said. His recommendation is to first use the "Supported kernel from your favorite Linux distribution". He further goes on to explain that security fixes and critical patches are backported to both Latest LTS and Older LTS releases, which are maintained by the kernel dev's. In Slackware's situation PV's supported kernel for stable is 4.4.153, an Older LTS release. For Slackware's current branch PV is including 4.14.67, the Latest LTS release. Both are very recent and include critical security patches. Both have long term support from kernel dev's. Those are the kernel's you should consider using and there aren't any 'politics' involved. If you want support for Slackware stable then you should be running the 4.4.153 kernel or build the latest version 4.4 if you want. If you want support for current then the 4.14.67 kernel is the Latest LTS available. If your opinion is that your Slackware should be running 4.18 then you can certainly compile it from kernel.org, but don't expect PV to support it. PV indicated he has run in to issues with newer 4.4 versions with UEFI system testing, I appreciate that he is testing newer kernels and I don't find black screens by compile and building myself. (Update: with release of 4.4.153 PV indicated he has resolved the UEFI issue)
Cheers, BrianA_MN
Last edited by bamunds; 08-28-2018 at 09:50 PM.
Reason: Update for new kernels released on 28/08/2018 by PV.
Um no, that is not what Greg said. His recommendation is to first use the "Supported kernel from your favority Linux distribution". He further goes on to explain that security fixes and critical patches are backported to the both Latest LTS and Older LTS releases, which are maintained by kernel dev's. In Slackware's situation PV's supported kernel for stable is 4.4.144, and Older LTS release. For Slackware's current branch PV is including 4.14.67, the Latest LTS release. Both are very recent and include critical security patches. Both have long term support from kernel dev's. Those are the kernel's you should consider using and there aren't any 'politics' involved. If you want support for Slackware stable then you should be running the 4.4.144 kernel or build the latest version 4.4 if you want. If you want support for current then the 4.14.67 kernel is the latest LTS available. If your opinion is that Slackware should be running 4.18 then you can certainly compile it from kernel.org, but don't expect PV to support it. PV indicated he has run in to issues with newer 4.4 versions with UEFI system testing, I appreciate that he is testing newer kernels and I don't find black screens by compile and building myself.
Cheers, BrianA_MN
The Supported kernel from your favority distribution, in the case of Slackare, is a LTS kernel of kernel.org, because Pat use vanilla sources. When Slacware current go to stable the kernel only changes by security reasons. And here is the problem because Greg (and Linus) do not distinguish between security patches and others patches. All patches that go to LTS are security patches (again, this is what Linus and Greg say, not me).
Considering that the 4.19.x will be LTS, I suspect that its first releases to be, well... problematic.
I observed the tendency of the kernel developers to push into next LTS tons of code (which some is somehow questionable as functionality), considering that the things will be polished later.
See the adventures with the 4.14.x now used by -current. So, maybe our BDFL will consider to push the future 4.19.x firstly into /testing
Last edited by Darth Vader; 08-27-2018 at 05:32 PM.
Considering that the 4.19.x will be LTS, I suspect that its first releases to be, well... problematic.
I observed the tendency of the kernel developers to push into next LTS tons of code (which some is somehow questionable as functionality), considering that the things will be polished later.
See the adventures with the 4.14.x now used by -current. So, maybe our BDFL will consider to push the future 4.19.x firstly into /testing
Just curious, where did you read that 4.19 will be a LTS release?
Cheers Wiz, new kernels aren't official until you've announced them
News! News! In addition to 4.17 now being EOL, lots of people have guessed that 4.19 will have long term support, and it looks like that's officially maybe going to happen: https://www.kernel.org/category/releases.html
Last edited by Darth Vader; 08-27-2018 at 09:00 PM.
Ok not arguing because I agree that it will probably be a LTS kernel. but right now it says "TBD" to be determined, so that tell me there is no official response that 4.19 will be long term.
Ok not arguing because I agree that it will probably be a LTS kernel. but right now it says "TBD" to be determined, so that tell me there is no official response that 4.19 will be long term.
OR, that "TBD" stands just for the fact that Linus Torvalds does not yet decided those dates...
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,087
Original Poster
Rep:
The security patched 4.4.153 kernel for Slackware-14.2 is now available.
Quote:
Tue Aug 28 22:05:19 UTC 2018
patches/packages/linux-4.4.153/*: Upgraded.
This kernel update enables mitigations for L1 Terminal Fault aka
Foreshadow and Foreshadow-NG vulnerabilities.
Thanks to Bernhard Kaindl for bisecting the boot issue that was preventing
us from upgrading to earlier 4.4.x kernels that contained this fix.
To see the status of CPU vulnerability mitigations on your system, look at
the files in: /sys/devices/system/cpu/vulnerabilities
Be sure to upgrade your initrd after upgrading the kernel packages.
If you use lilo to boot your machine, be sure lilo.conf points to the correct
kernel and initrd and run lilo as root to update the bootloader.
If you use elilo to boot your machine, you should run eliloconfig to copy the
kernel and initrd to the EFI System Partition.
For more information, see: https://cve.mitre.org/cgi-bin/cvenam...=CVE-2018-3615 https://cve.mitre.org/cgi-bin/cvenam...=CVE-2018-3620 https://cve.mitre.org/cgi-bin/cvenam...=CVE-2018-3546
(* Security fix *)
+--------------------------+
Last edited by cwizardone; 08-28-2018 at 10:42 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
