LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-12-2018, 11:17 AM   #1
Xsane
Member
 
Registered: Jan 2014
Posts: 146

Rep: Reputation: 110Reputation: 110
14.1 spectre/meltdown status?


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.
 
Old 03-12-2018, 06:06 PM   #2
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 1,585

Rep: Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834
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.

Opinions welcome
 
Old 03-12-2018, 06:20 PM   #3
Skaendo
Member
 
Registered: Dec 2014
Location: West Texas, USA
Distribution: Slackware64-14.2
Posts: 754

Rep: Reputation: Disabled
Quote:
Originally Posted by Xsane View Post
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?
 
Old 03-12-2018, 06:25 PM   #4
allend
LQ Guru
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,010

Rep: Reputation: 1754Reputation: 1754Reputation: 1754Reputation: 1754Reputation: 1754Reputation: 1754Reputation: 1754Reputation: 1754Reputation: 1754Reputation: 1754Reputation: 1754
Quote:
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.
 
Old 03-12-2018, 06:30 PM   #5
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 1,585

Rep: Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834
Quote:
Originally Posted by allend View Post
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.
 
7 members found this post helpful.
Old 03-12-2018, 07:50 PM   #6
dgrames
Member
 
Registered: Jul 2007
Distribution: Slackware
Posts: 64

Rep: Reputation: 13
I'm not sure if this is helpful, but I compiled gcc-5.5.0 from the 14.2 source on a 14.1 virtual machine. Then I compiled a 4.9.81 kernel.

Seems to be OK.
I'm working on migration of that server to a 14.2 server.
 
1 members found this post helpful.
Old 03-13-2018, 06:49 AM   #7
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,426

Rep: Reputation: 831Reputation: 831Reputation: 831Reputation: 831Reputation: 831Reputation: 831Reputation: 831
Quote:
Originally Posted by volkerdi View Post
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.

Opinions welcome
volkerdi --

Boy ... I don't have an opinion, only questions.

Yes, linux-3.10.y is dead.

Willy Tarrau announced EoL for the 3.10.y Kernel on 4 Nov 2017 but Ben Hutchings is keeping the 3.2.y Kernels going indefinitely.

The last 3.10.y release was linux-3.10.108:

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 ?

Sadly, the days of installing an maintaining a single version of Slackware until a Machine is retired may be behind us ?

-- kjh

Last edited by kjhambrick; 03-13-2018 at 06:54 AM. Reason: add lwn link
 
Old 03-14-2018, 11:05 AM   #8
allend
LQ Guru
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,010

Rep: Reputation: 1754Reputation: 1754Reputation: 1754Reputation: 1754Reputation: 1754Reputation: 1754Reputation: 1754Reputation: 1754Reputation: 1754Reputation: 1754Reputation: 1754
Quote:
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.
 
1 members found this post helpful.
Old 03-14-2018, 02:03 PM   #9
ttk
Member
 
Registered: May 2012
Location: Sebastopol, CA
Distribution: Slackware64
Posts: 722
Blog Entries: 25

Rep: Reputation: 869Reputation: 869Reputation: 869Reputation: 869Reputation: 869Reputation: 869Reputation: 869
Quote:
Originally Posted by kjhambrick View Post
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.
 
1 members found this post helpful.
Old 03-14-2018, 03:43 PM   #10
upnort
Member
 
Registered: Oct 2014
Distribution: Slackware, Proxmox, Debian, CentOS, Ubuntu MATE
Posts: 708

Rep: Reputation: Disabled
Quote:
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.

Last edited by upnort; 03-14-2018 at 03:45 PM.
 
3 members found this post helpful.
Old 03-14-2018, 05:26 PM   #11
jmccue
Member
 
Registered: Nov 2008
Location: US
Distribution: slackware
Posts: 284

Rep: Reputation: 133Reputation: 133
IGNORE

Deleted a 14.2 specific response, I have the flu and a bit out of it and did not notice 14.1

Last edited by jmccue; 03-14-2018 at 05:35 PM. Reason: added IGNORE -- missed real question
 
Old 03-14-2018, 06:04 PM   #12
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 1,585

Rep: Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834Reputation: 4834
Quote:
Originally Posted by jmccue View Post
Deleted a 14.2 specific response, I have the flu and a bit out of it and did not notice 14.1
Hope you feel better soon.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Meltdown/Spectre Status for Red Hat and Oracle LXer Syndicated Linux News 0 02-06-2018 03:40 AM
[SOLVED] Spectre & Meltdown gillsman Linux - Newbie 2 01-28-2018 08:12 AM
Vulnerabilities such as Meltdown and Spectre caseyl Linux - Security 7 01-22-2018 09:14 PM
Meltdown and Spectre ots3go Solaris / OpenSolaris 1 01-10-2018 04:15 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 10:10 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration