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.
yep, 4.18.3 4.17.17 4.14.65 4.9.122 and 4.4.150 just arrived. Apparently the l1tf "fix" was bad.
I hope nobody in the real world is using Intel SGX. Calling this a "vulnerability" is a bit disingenuous. From the MPAA's point of view, it is, but from the computer owner's point of view, it isn't
I follow slackware64-current on my laptop and install all upgrades as they come along. It's just a personal computer and there's nothing on here I need to worry about so I'm quite happy just to follow the changelog along.
I keep two kernels always, the one that's working is the default one that boots and the newest one. I have to recompile the driver for my wireless dongle each time, again no problem, so I always use the huge.s kernel rather than a generic one as the kernel updates are so frequent.
This is what I wanted to ask about. With Slackware being the way it is, nothing is updated until it is stable and proven and I know we are talking about current here so things maybe a little more edgy but still, even current is generally a pretty stable os. There's never a time that I sit here with the xserver crashing or a laptop that refuses to boot due to some 'bleeding edge' update. So what is the story with the current kernels? Is it a particular branch that Pat follows and therefore issues the updates as and when they appear? Or does he have particular criteria that mean the next one may be added in to the changelog only if he's happy?
I only ask because since I have been tracking current I have been updating the kernel more than anything else and I just wondered why.
This is what I wanted to ask about. With Slackware being the way it is, nothing is updated until it is stable and proven and I know we are talking about current here so things maybe a little more edgy but still, even current is generally a pretty stable os. There's never a time that I sit here with the xserver crashing or a laptop that refuses to boot due to some 'bleeding edge' update. So what is the story with the current kernels? Is it a particular branch that Pat follows and therefore issues the updates as and when they appear? Or does he have particular criteria that mean the next one may be added in to the changelog only if he's happy?
I got into the habit of taking the latest 4.14.x kernel when we were trying to help debug the crash issues that were happening early on, and then just kind of stuck with it. But with the Meltdown, Spectre, and related vulnerabilities getting new mitigations often, it's probably not a bad habit to be in.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.