LinuxQuestions.org
Visit the LQ Articles and Editorials section
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 05-14-2013, 08:52 AM   #46
cynwulf
Senior Member
 
Registered: Apr 2005
Distribution: OpenBSD, Slackware
Posts: 1,223

Rep: Reputation: 379Reputation: 379Reputation: 379Reputation: 379

3.8.x is working well for me, since 3.8.10 a hard lock up problem I was getting in 3.x kernels has been resolved. I would use 3.4, but due to the aforementioned problem will have to wait for the next LTS to appear... it's annoying but what can you do.
 
Old 05-14-2013, 09:29 AM   #47
GazL
Senior Member
 
Registered: May 2008
Posts: 3,319

Rep: Reputation: 881Reputation: 881Reputation: 881Reputation: 881Reputation: 881Reputation: 881Reputation: 881
Well, Pat could always delay the release until around Christmas and ship with the next LTS once it's been released and had time to settle in. Actually, that doesn't sound so bad: one new Slackware release each year, somewhere around Christmas, each one based off a new LTS kernel, guaranteeing two years of upstream kernel support for each Slackware release.

 
Old 05-14-2013, 09:29 AM   #48
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
3.10 might be a good bet
http://lkml.indiana.edu/hypermail/li...5.1/02192.html
 
Old 05-14-2013, 11:01 AM   #49
PrinceCruise
Member
 
Registered: Aug 2009
Location: /Universe/Earth/India/Pune
Distribution: Slackware64 14.1/Current, CentOS 6.5/7.0
Posts: 713

Rep: Reputation: Disabled
Quote:
Originally Posted by GazL View Post
Well, Pat could always delay the release until around Christmas and ship with the next LTS once it's been released and had time to settle in. Actually, that doesn't sound so bad: one new Slackware release each year, somewhere around Christmas, each one based off a new LTS kernel, guaranteeing two years of upstream kernel support for each Slackware release.
+1. I'm also in the same favor and requested the same in the 14.1 voting thread.

Regards.
 
1 members found this post helpful.
Old 05-14-2013, 11:29 AM   #50
Petri Kaukasoina
Member
 
Registered: Mar 2007
Posts: 241

Rep: Reputation: 86
Kernel 3.8.y.z extended stable support
http://lkml.indiana.edu/hypermail/li...5.1/03595.html
 
1 members found this post helpful.
Old 05-14-2013, 12:24 PM   #51
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
Quote:
Originally Posted by Petri Kaukasoina View Post
Kernel 3.8.y.z extended stable support
http://lkml.indiana.edu/hypermail/li...5.1/03595.html
Quote:
Since Ubuntu 13.04 "Raring" uses the 3.8 kernel, the Ubuntu kernel team
will pick up stable maintenance where Greg KH left off[0] with 3.8.13
(thanks, Greg!)...


The Ubuntu kernel team is pleased to announce that we will be providing
extended stable support for the Linux 3.8 kernel until August 2014 as a
third party effort maintained on our infrastructure.

Our linux-3.8.y{-queue,-review} stable branches will fork from 3.8.13
and will be published here:

git://kernel.ubuntu.com/ubuntu/linux.git

We will use the same stable request/review workflow and follow the
standard upstream stable kernel rules. More details are available at
http://wiki.ubuntu.com/Kernel/Dev/ExtendedStable

We welcome any feedback and contribution to this effort. We will be
posting the first review cycle patch set in a week or two.

-Kamal Mostafa
Ubuntu Kernel Team, Canonical Ltd.
That's great news, maybe 3.8 can be kept after all in current. I wonder if they will apply any out of tree patches tho.
 
Old 05-14-2013, 12:31 PM   #52
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Gentoo
Posts: 15,402
Blog Entries: 2

Rep: Reputation: 3993Reputation: 3993Reputation: 3993Reputation: 3993Reputation: 3993Reputation: 3993Reputation: 3993Reputation: 3993Reputation: 3993Reputation: 3993Reputation: 3993
Quote:
Originally Posted by H_TeXMeX_H View Post
That's great news, maybe 3.8 can be kept after all in current. I wonder if they will apply any out of tree patches tho.
From the link in your quote:
Quote:
All patches for the stable releases maintained by the Ubuntu kernel team should be submitted upstream, following the stable upstream acceptance rules (see Documentation/stable_kernel_rules.txt in the upstream kernel source tree for more information).

The Ubuntu Kernel Team should monitor and pick the relevant stable patches automatically once they are released with upstream stable.
So as I understand it they only apply patches released by upstream, so no out of tree patches.
 
Old 05-14-2013, 12:34 PM   #53
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,502

Rep: Reputation: 405Reputation: 405Reputation: 405Reputation: 405Reputation: 405
well it's basically the same approach used by Greg
patches that goes into stable kernel are usually found on upstream tree (linus' tree) that goes on development for the next RC or final version of the next major release
 
Old 05-14-2013, 04:03 PM   #54
Celyr
Member
 
Registered: Mar 2012
Location: Italy
Distribution: Slackware+Debian
Posts: 314

Rep: Reputation: 77
Quote:
All patches for the stable releases maintained by the Ubuntu kernel team ...
Quote:
... Ubuntu kernel team ...
Ubuntu kernel team
Ubuntu kernel team
Mother of God.



(sorry :P)
 
3 members found this post helpful.
Old 05-14-2013, 05:56 PM   #55
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,014

Rep: Reputation: 145Reputation: 145
Quote:
Originally Posted by Petri Kaukasoina View Post
Kernel 3.8.y.z extended stable support
http://lkml.indiana.edu/hypermail/li...5.1/03595.html
Thanks for the info!

However, I would quote a bit of that article: "... until August 2014 ..."
 
Old 05-15-2013, 01:17 AM   #56
dolphin77
Member
 
Registered: May 2009
Posts: 200

Rep: Reputation: 54
Looks like kernels prior to 3.8.10 are not the safe choice currently (local root exploit):

http://packetstormsecurity.com/files/121616/semtex.c
 
Old 05-15-2013, 02:19 AM   #57
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 857

Rep: Reputation: 1667Reputation: 1667Reputation: 1667Reputation: 1667Reputation: 1667Reputation: 1667Reputation: 1667Reputation: 1667Reputation: 1667Reputation: 1667Reputation: 1667
Quote:
Originally Posted by dolphin77 View Post
Looks like kernels prior to 3.8.10 are not the safe choice currently (local root exploit):

http://packetstormsecurity.com/files/121616/semtex.c
The PERF_EVENTS bug is not present in 3.4.45 either.
 
1 members found this post helpful.
Old 05-15-2013, 10:03 AM   #58
Poprocks
Member
 
Registered: Sep 2003
Location: Toronto, Canada
Distribution: Slackware
Posts: 194

Rep: Reputation: 26
Quote:
Originally Posted by PrinceCruise View Post
+1. I'm also in the same favor and requested the same in the 14.1 voting thread.
Agreed. At this juncture, if Slack 14.1 were to come out *today* I'd even be tempted to say "3.2" because it *still* seems to be the longest-supported, being targetted for EOL in 2016 as opposed to 2014 or what have you.

Also, where is this 14.1 voting thread? I can't seem to find it on here.
 
Old 05-15-2013, 01:07 PM   #59
PrinceCruise
Member
 
Registered: Aug 2009
Location: /Universe/Earth/India/Pune
Distribution: Slackware64 14.1/Current, CentOS 6.5/7.0
Posts: 713

Rep: Reputation: Disabled
Quote:
Originally Posted by Poprocks View Post
Also, where is this 14.1 voting thread? I can't seem to find it on here.
Not really a 14.1 voting thread, but Pat asked for opinions on couple of things for next 'stable' release here -
This thread

Regards.
 
Old 05-17-2013, 10:51 PM   #60
michaelslack
Member
 
Registered: Feb 2013
Location: Sydney
Distribution: slackware
Posts: 79

Rep: Reputation: 25
If -current(64) goes back to 3.4 then will the dreaded samsung-laptop bricking problem be an issue again? Fixes for that (such as they were) were introduced late in the 3.7 series I believe.
 
  


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
[SOLVED] Kernel 3.7.1 keyboard's dead RoyBatty100 Slackware 2 03-06-2013 11:41 PM
LXer: Openmoko Gets New Life in Brazil After Being Declared Dead LXer Syndicated Linux News 0 07-14-2009 09:30 AM
Dead kernel link B4lulu Linux - Newbie 4 08-28-2007 10:30 PM
Kernel updated, now Internet dead dmorrell Linux - Networking 1 04-26-2006 03:40 AM
keyboard dead with kernel 2.6.4 matrixfx Linux - Hardware 2 03-26-2004 10:06 PM


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

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration