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.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Original Poster
Rep:
Quote:
Originally Posted by abga
I was almost convinced you abandoned the thread (&us) ...
Nah.
"He with the hyphenated surname" has slowed down for whatever reasons. Recently he has been putting out kernel updates at a rate of one every 7 to 9 days, instead every three or four days.
Last edited by cwizardone; 11-03-2019 at 04:39 PM.
That sounds encouraging.... I get the feeling that releases are tested mostly by bots on
virtual machines, not so much on real hardware.
I hate regressions; With the ever increasing complexity in the kernel it's sometimes very
hard to pin the problem down enough to even write a meningful bug report that actually helps.
Luckily I haven't found any problems yet, apart from a compile failure in net, with 5.4-rc's
Let's hope for a problem free 5.4.
I decided to update every tenth release starting from 4.19.80. There's really no need to update so frequently. It also gives me time to actually test the kernel.
I decided to update every tenth release starting from 4.19.80. There's really no need to update so frequently. It also gives me time to actually test the kernel.
I'm still on 4.19.76. Two reasons - I really see no need to update so frequently, and secondly I'm seeing how long an uptime I can get on this laptop. When I first installed -current, regular kernel updates were a nice exercise in learning and getting the latest version up on neofetch shots, but really, I don't see it as worth doing unless there's a big change to the kernel [and it would have to be pretty big for me to move at the moment].
Last edited by Lysander666; 11-04-2019 at 04:53 AM.
In the past I have experienced uptimes of over 13 months, at least twice. These days though kernel changes are often bigger and faster. If you have AMD/Ati Graphics there is substantial value in upgrading as so much development is going on there. Phoronix and others say all gamers will likely see substantial gains with the 5.4x kernels, which translates into anyone involved in heavier mutlimedia loads will benefit. So upgrading frequency seems to be hardware and software niche related but there is no solid reason not to stay with whatever works for you on any given system. If it ain't broke....
I may see if 5.4-rc6 and newest nVidia have resolved their differences yet on -Current. My Main 14.2 MultiLib keeps humming along sweetly on 5.0.20
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.