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.
Pat, could you please tell us the status of 14.1 with regard to the
spectre/meltdown vulnerability? Will there be any package updates to
address the issue? Thanks.
Status is that the 3.10.x kernel seems completely dead upstream, which is a bit odd since 3.2.x is still getting fixes.
I could try to put out a kernel update for 14.1 from a newer branch, but I'm going to be honest here and say that's probably more disruptive for the average user than the spectre/meltdown vulnerabilities are likely to be. I could do it, though.
Pat, could you please tell us the status of 14.1 with regard to the
spectre/meltdown vulnerability? Will there be any package updates to
address the issue? Thanks.
Maybe this might be better addressed to Linus and Co.? But then again considering his attitude/feelings about the whole situation it might be better to leave them alone?
Mon Nov 4 17:08:47 UTC 2013
Slackware 14.1 x86 stable is released!
As Slackware 14.1 turns 5 years old this year, I would consider it a legacy release that is approaching EOL, so requiring only minimal maintenance effort.
As Slackware 14.1 turns 5 years old this year, I would consider it a legacy release that is approaching EOL, so requiring only minimal maintenance effort.
Speaking of which, we need to declare EOL soon on those 13.x releases. They've become too old to give proper support to.
Status is that the 3.10.x kernel seems completely dead upstream, which is a bit odd since 3.2.x is still getting fixes.
I could try to put out a kernel update for 14.1 from a newer branch, but I'm going to be honest here and say that's probably more disruptive for the average user than the spectre/meltdown vulnerabilities are likely to be. I could do it, though.
Speaking of which, we need to declare EOL soon on those 13.x releases. They've become too old to give proper support to.
The right decision.
I am probably crying in my cups, but I will always have soft spot for 'leet'. It harks back to when the open source source movement was at a height; before virtual server farms, systemd and cloud computing became the fashion.
Vale 'leet', an historic release, which is a glowing testament to the efforts of all who brought it to fruition.
Willy recommended going to the 4.4.y Kernel in his blog but ...
What are the implications of sliding a new Kernel along with the matching Kernel Headers beneath a running legacy system -vs- upgrading Slackware ?
My most heavily-used systems are 64-bit 14.1 (office desktop, home desktop, everyday-use laptop, home fileserver), and I have not yet encountered a problem with running them on the 4.4.118 kernel from the 14.2 release.
Of course the packages I use might be different from the packages you use, so your experiences might not match mine. Perhaps try it in a test environment and see if any problems crop up.
The impact of migrating to 14.2 is entirely specific to your situation, but if you haven't started at least testing it, you probably should. 14.1 still has legs, but it won't remain viable forever.
Sadly, the days of installing an maintaining a single version of Slackware until a Machine is retired may be behind us?
Pat is one of the exceptions to supporting software long term. Otherwise, developers and distro maintainers in free/libre software seem hell-bent to obsolete software as fast as possible, which obsoletes hardware too.
With respect to 14.1, methinks don't directly expose the system to the a**-wipes of the world. The biggest hole with Meltdown/Spectre is JavaScript in web browsers. Don't use a web browser in 14.1 and that reduces the potential for exploit.
Back in January 2017 I migrated several 14.1 systems to 14.2, well after 14.2 was released. Just one system at a time, noting the hiccups and then moving to the next system. I first transitioned all systems from 14.1 32-bit to 14.1 64-bit before updating to 14.2 64-bit. There were some hiccups but nothing traumatic. I shared some of the details online. Start with "Preparing For The Big Update" in January 2017 and then continue into the April entries. I hope that helps.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.