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.
|
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.
:D |
3.10 might be a good bet
http://lkml.indiana.edu/hypermail/li...5.1/02192.html |
Quote:
Regards. |
Kernel 3.8.y.z extended stable support
http://lkml.indiana.edu/hypermail/li...5.1/03595.html |
Quote:
Quote:
|
Quote:
Quote:
|
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 |
Quote:
Quote:
Ubuntu kernel team Mother of God. (sorry :P) |
Quote:
However, I would quote a bit of that article: "... until August 2014 ..." |
Looks like kernels prior to 3.8.10 are not the safe choice currently (local root exploit):
http://packetstormsecurity.com/files/121616/semtex.c |
Quote:
|
Quote:
Also, where is this 14.1 voting thread? I can't seem to find it on here. |
Quote:
This thread Regards. |
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.
|
All times are GMT -5. The time now is 02:38 AM. |