Kernel Longevity - Making the same mistakes again?
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.
Of course this rarely happens, the NPTL implementation of pthreads is the only relevant info I found about Linux kernel version compatibility in glibc docs
Click here to see the post LQ members have rated as the most helpful post in this thread.
Given that 3.0 has been announced as a long-term kernel by Greg K-H and will be supported for at least 2 years, wouldn't it make sense to stick with this as the official stock kernel in current, and provide any later ones in extra/ ?
For my own selfish reasons, my answer is "no".
2nd Gen Sandy Bridge hardware is broken on 3.0.X imo.
Also realteak and broadcom wireless have so many connect/reconnects as well.
These issues seem fixed in 3.1.7 and greater.
Tho 3.2.2 had some funky wifi drops/resets as well, but they've been fixed in 3.2.4
Well, Greg is the upstream stable kernel maintainer, so I'm inclined to pay attention to what he says, but fair enough.
It is likely that other distros who have their own kernel teams will maintain their own patch-sets, but I don't think many Slackers are likely to use a Redhat or Canonical patch-set over a kernel.org kernel, but I guess it is possible.
I guess Tim Garder will take over kernel.org 3.2: https://lkml.org/lkml/2012/1/11/91
I don't think it's more of a problem for Slackware users that he works for Canonical than it has been a problem that Greg has worked for SUSE.
Can you point me to the patches that are supposed to fix wifi drops? I would like to test this.
sure, ftp://ftp.kernel.org/pub/linux/kerne...Log-3.2.33.2.3 & 3.2.4 are effectively the same so here's the changelog.Prior to this fix, I had wicd rmmod all the wifi modules the modprobe them back, restart my net services and then rejoin the wifi network.Thanks to this fix, my wicd scripts directory is empty now
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.