LinuxQuestions.org
Review your favorite Linux distribution.
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 02-08-2019, 10:30 AM   #1171
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,461

Original Poster
Blog Entries: 1

Rep: Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777

Kernel update 4.4.174 is now available at

https://www.kernel.org/

The change log, https://cdn.kernel.org/pub/linux/ker...ngeLog-4.4.174


Dave's Unofficial Slackbuilt Kernel update for the 4.4.y series
can be found at, https://dusk.idlemoor.tk
 
2 members found this post helpful.
Old 02-10-2019, 05:52 PM   #1172
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,461

Original Poster
Blog Entries: 1

Rep: Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777
5.0-rc6

The newest "mainline" kernel, version 5.0-rc6, has been been made available for testing.

The tarball, https://git.kernel.org/torvalds/t/linux-5.0-rc6.tar.gz

Mr. Torvalds' announcement, http://lkml.iu.edu/hypermail/linux/k...2.1/01729.html
Quote:
.....nothing in there looks all that odd or scary. I think we're still solidly on track for a normal release.

Last edited by cwizardone; 02-10-2019 at 06:54 PM.
 
1 members found this post helpful.
Old 02-11-2019, 03:09 PM   #1173
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,461

Original Poster
Blog Entries: 1

Rep: Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777
Kernel update 3.16.63 is now available at

https://www.kernel.org/

The change log, https://cdn.kernel.org/pub/linux/ker...ngeLog-3.16.63
 
1 members found this post helpful.
Old 02-12-2019, 02:27 PM   #1174
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,461

Original Poster
Blog Entries: 1

Rep: Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777
Kernel updates 4.20.8, 4.19.21, 4.14.99 and 4.9.156 are now available at

https://www.kernel.org/

The change logs,

https://cdn.kernel.org/pub/linux/ker...angeLog-4.20.8

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.19.21

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.14.99

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.9.156

Both the 4.20.8 and 4.19.21 change logs reference CVE-2019-3819, CVE-2019-6974, CVE-2019-7221 and CVE-2019-7222.

The 4.14.99 and 4.9.156 change logs reference CVE-2019-6974, CVE-2019-7221 and CVE-2019-7222.

Last edited by cwizardone; 02-12-2019 at 04:07 PM.
 
4 members found this post helpful.
Old 02-14-2019, 09:29 AM   #1175
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,461

Original Poster
Blog Entries: 1

Rep: Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777
Since installing the 4.19.21 kernel I've been experiencing random complete freezes of the system and have reverted to the 4.19.20 kernel.

There is another round of kernel updates scheduled for Friday evening UTC/GMT. We'll see if 4.19.22 fixes the problem.
On a probably unrelated matter, Adobe-Reader-9.5.5.1, which has worked for years on my Multilib system, no longer works with the 4.19.20 or 4.19.21 kernels. It did work with the 4.19.19 kernel. Good thing Okular is almost "there."

Acroread will start and you can look at the different commands on the tool bar, but the moment I click on "Open," it crashes, i.e., disappears in a flash with this error,

Quote:
dirname: missing operand
A search did produce this,
https://www.linuxquestions.org/quest...roread-827012/

OK. Found it and it had already been changed as recommended above.

Just found this,

https://www.linuxquestions.org/quest...er-4175413543/

Nope. Doesn't fix the problem.

Last edited by cwizardone; 02-14-2019 at 03:42 PM. Reason: Typo.
 
2 members found this post helpful.
Old 02-15-2019, 04:19 AM   #1176
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,461

Original Poster
Blog Entries: 1

Rep: Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777
Kernel updates 4.20.10, 4.19.23, 4.14.101 and 4.9.158 are now available at

https://www.kernel.org/

The change logs,

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.20.10

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.19.23

https://cdn.kernel.org/pub/linux/ker...geLog-4.14.101

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.9.158

It looks like a number has been skipped in each series, but an explanation has yet to be posted.

OK, here is a twist some of you may appreciate.
Each of the next number in sequence were announced with a message similar to this one,
Quote:
Linux 4.19.22
From: Greg KH
Date: Fri Feb 15 2019 - 04:24:14 EST

I'm announcing the release of the 4.19.22 kernel.

Don't use this, use 4.19.23 instead.........

thanks,

greg k-h
Then each of the following number in each series was announced with the usual, "All users must upgrade" message.

Each Change log only has one entry,
Quote:
commit 67d52fae61c152a68924d94dcf0c569a96fa2f5d
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date: Fri Feb 15 09:09:54 2019 +0100

Linux 4.19.23

commit c2109f05b7fd5d2e5472f45dbcc343786c504719
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Thu Feb 14 15:02:18 2019 -0800

Revert "exec: load_script: don't blindly truncate shebang string"

commit cb5b020a8d38f77209d0472a0fea755299a8ec78 upstream.

This reverts commit 8099b047ecc431518b9bb6bdbba3549bbecdc343.

It turns out that people do actually depend on the shebang string being
truncated, and on the fact that an interpreter (like perl) will often
just re-interpret it entirely to get the full argument list.

Reported-by: Samuel Dionne-Riel <samuel@dionne-riel.com>
Acked-by: Kees Cook <keescook@chromium.org>
Cc: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Last edited by cwizardone; 02-15-2019 at 05:15 AM.
 
1 members found this post helpful.
Old 02-15-2019, 08:15 AM   #1177
blancamolinos
Member
 
Registered: Mar 2011
Distribution: Slackware
Posts: 79

Rep: Reputation: 54
It seems clear that Slackware has a problem taking its kernels from the so-called LTS kernels that are generated by kernel.org.
 
Old 02-15-2019, 08:17 AM   #1178
Petri Kaukasoina
Member
 
Registered: Mar 2007
Posts: 389

Rep: Reputation: 246Reputation: 246Reputation: 246
What problem?
 
Old 02-15-2019, 08:19 AM   #1179
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Slackware, Ubuntu
Posts: 1,234
Blog Entries: 3

Rep: Reputation: 1220Reputation: 1220Reputation: 1220Reputation: 1220Reputation: 1220Reputation: 1220Reputation: 1220Reputation: 1220Reputation: 1220
Quote:
Originally Posted by blancamolinos View Post
It seems clear that Slackware has a problem taking its kernels from the so-called LTS kernels that are generated by kernel.org.
The latest kernel for the 4.4.xxx series on kernel.org is 4.4.174; Slackware stable is on 4.4.172. My understanding is that Pat tweaks or adapts the 4.4.xxx kernels specifically for Slackware and only when there are important bug fixes that need addressing.

I'm personally not going to move to 4.4.174 just for the sake of it and Patrick knows what's good for Slackware a lot more than I do.

Last edited by Lysander666; 02-15-2019 at 08:21 AM.
 
2 members found this post helpful.
Old 02-15-2019, 09:40 AM   #1180
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,461

Original Poster
Blog Entries: 1

Rep: Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777Reputation: 1777
Quote:
Originally Posted by blancamolinos View Post
It seems clear that Slackware has a problem taking its kernels from the so-called LTS kernels that are generated by kernel.org.

Would you be kind enough to clarify that statement?
As it stands, it make no sense at all.
Thanks.
 
1 members found this post helpful.
Old 02-15-2019, 10:12 AM   #1181
blancamolinos
Member
 
Registered: Mar 2011
Distribution: Slackware
Posts: 79

Rep: Reputation: 54
The policy Slackware has historically followed to include kernels from kernel.org (only in some cases Patrick has skipped this by applying individual patches to the kernel in stable) is valid if the kernel.org LTS kernels are what LTS is supposed to mean . But lately it has been possible to verify that these kernels introduce changes that break the compatibility and also do not seem to have been tested.
 
Old 02-15-2019, 10:14 AM   #1182
Poprocks
Member
 
Registered: Sep 2003
Location: Toronto, Canada
Distribution: Slackware
Posts: 367

Rep: Reputation: 164Reputation: 164
Yeah, no, that is completely false, blancamolinos, and I have no idea where you are getting that information from. Slackware has used an LTS kernel branch for every release since (at least) Slackware 14.0.
 
2 members found this post helpful.
Old 02-15-2019, 10:32 AM   #1183
blancamolinos
Member
 
Registered: Mar 2011
Distribution: Slackware
Posts: 79

Rep: Reputation: 54
I do not remember the version where this happened but the context: to solve a security problem in the kernel Patrick took the most recent LTS version but this introduced problems with the graphics. After several attempts, I think it was 3, Patrick chose to apply only the security patch on the kernel that was in Slackware stable.
 
Old 02-15-2019, 10:50 AM   #1184
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Slackware, Ubuntu
Posts: 1,234
Blog Entries: 3

Rep: Reputation: 1220Reputation: 1220Reputation: 1220Reputation: 1220Reputation: 1220Reputation: 1220Reputation: 1220Reputation: 1220Reputation: 1220
Quote:
Originally Posted by blancamolinos View Post
I do not remember the version where this happened but the context: to solve a security problem in the kernel Patrick took the most recent LTS version but this introduced problems with the graphics. After several attempts, I think it was 3, Patrick chose to apply only the security patch on the kernel that was in Slackware stable.
Maybe this will go some way to explaining?
 
1 members found this post helpful.
Old 02-15-2019, 11:47 AM   #1185
blancamolinos
Member
 
Registered: Mar 2011
Distribution: Slackware
Posts: 79

Rep: Reputation: 54
This is the exception i remembered, from Slackware64 version 14.0 stable changelog:

+--------------------------+
Mon Jun 3 22:10:16 UTC 2013
patches/packages/linux-3.2.45/*: Rebuilt.
One more reverted commit. This one was leading to hangs on systems with
Intel graphics. The previous revert was also reverted in 3.2.46, but it
seems safer to just get this one manually than to take the newer kernel and
still have to do another patch to it anyway. Hopefully the third time is
the charm.
+--------------------------+
Wed May 22 14:11:13 UTC 2013
patches/packages/linux-3.2.45/*: Rebuilt.
It appears a bad commit slipped into 3.2.45 and it's causing problems on
systems that use Intel graphics. The commit has been reverted in the kernel
source packages and the kernels and modules have been rebuilt. If you ran
into the black screen problem before, this should fix it up.
+--------------------------+
Mon May 20 21:01:33 UTC 2013
patches/packages/linux-3.2.45/*: Upgraded.
Upgraded to new kernels that fix CVE-2013-2094, a bug that can allow local
users to gain a root shell. Be sure to upgrade your initrd and reinstall
LILO after upgrading the kernel packages.
For more information, see:
http://cve.mitre.org/cgi-bin/cvename...=CVE-2013-2094
(* Security fix *)
+--------------------------+
 
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
Linux.conf.au: Latest Linux kernel release due early March DragonSlayer48DX Linux - News 0 01-18-2010 11:43 PM
No video on latest kernel release Tralce Linux - Kernel 3 11-30-2006 08:48 AM
What is the latest Redhat release TILEMANN Linux - Software 5 11-20-2006 11:48 PM
LXer: News: OpenVZ To Release Support, Patches for Latest Kernel LXer Syndicated Linux News 0 11-01-2006 11:54 PM
latest debian release? doralsoral Linux - Software 5 12-25-2004 01:40 PM

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

All times are GMT -5. The time now is 02:35 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