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.
View Poll Results: When do you update/upgrade the kernel ?
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
Well, actually, nothing does -- I keep everything at stable. But I remember when there was a kernel update in... uh, 12.1? That I did do. And, on the other hand, I suppose that when a release is published and the DVD arrives in the mail the kernel might just be an upgrade, eh?
I really value stability and predictability -- the servers run for months -- over hairy edge; I suppose that was one of the reasons for picking Slackware in the first place.
On my server, I'm using the kernel shipped with Slackware.
On my desktop, I'm following the 3.8 branch of kernel.org, because my graphics card works better with that. Otherwise I would be using the stock kernel on desktop also.
I prefer one of the stable LTS branches, unless Slackware comes with an even newer kernel. In this case I wait for a LTS kernel. I always build a custom kernel and keep it up to date for all fixes. I do consider features in the kernel, such as video card support, but currently that's no longer an issue for me.
I'd be more comfortable staying back level if the kernel devs did a better job of announcing security issues, but given their tendency to silently fix security issues without telling people I tend to follow the latest stable branch from kernel.org. I'll usually hold off on a new branch until .1 or .2 though as the .1 and .2 changelogs always give me the feeling that the new mainline kernel releases could have really done with an extra RC or two.
I'm starting to question the value of LTS kernels though - I'm no longer sure they really buy you anything.
I'd be more comfortable staying back level if the kernel devs did a better job of announcing security issues, but given their tendency to silently fix security issues without telling people I tend to follow the latest stable branch from kernel.org. I'll usually hold off on a new branch until .1 or .2 though as the .1 and .2 changelogs always give me the feeling that the new mainline kernel releases could have really done with an extra RC or two.
I'm starting to question the value of LTS kernels though - I'm no longer sure they really buy you anything.
I agree, I do the same, except I follow the LTS kernels. I am hoping that they will be more stable than the latest stable.
I generally use the one that is in -current. However, I always compile a custom kernel about every month or so. Mainly just to do it for practice. One never knows when that skill may come in handy.
I mostly use the generic + initrd that comes with my version, but on the odd accassion when I have upgraded the kernel it has been to get a new device driver or due to a major security fix.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.