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.
This 6.7.y "stable" series has had a stupidly large number of patches each time. I was waiting for it to settle down, but it looks like that's not going to happen before 6.8 comes out.
This 6.7.y "stable" series has had a stupidly large number of patches each time. I was waiting for it to settle down, but it looks like that's not going to happen before 6.8 comes out.
I would be worried more if there wasn't a ton of patches. It means there's lots of fixes for the 6.8-rc kernels that are easy to backport to 6.7.x, that's why the most recent stable kernel series tends to have less bugs than LTS kernels.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,011
Rep:
Quote:
Originally Posted by GazL
This 6.7.y "stable" series has had a stupidly large number of patches each time. I was waiting for it to settle down, but it looks like that's not going to happen before 6.8 comes out.
only 6.7.y maybe whole 6.x.x or even earlier.
You are really understanding..
It means there's lots of fixes for the 6.8-rc kernels that are easy to backport to 6.7.x
Unfortunately, it also means there are a lot of bugs backported from the 6.8-rc's, especially during the early RC stages when things from the new RC are less mature and not widely tested. I usually skip the stable point releases that come out during the early RC's and update when the number of patches slows down. That hasn't really happened with this stable branch, which still seems extremely active.
P.S. I don't hold with the LTS releases either. I don't think they're a sensible proposition outside some niche use-cases (such as embedded). They're commonly thought of as a more stable choice, but as you rightly point out, that's simply not true.
fs/ntfs3: fix build without CONFIG_NTFS3_LZX_XPRESS
commit c8e314624a1666ed2eec28549713021a8ec801e9 upstream.
When CONFIG_NTFS3_LZX_XPRESS is not set then we get the following build
error:
fs/ntfs3/frecord.c:2460:16: error: unused variable ‘i_size’
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,125
Original Poster
Rep:
Quote:
Originally Posted by cwizardone
BTW, a few kernel versions ago some users were reporting they were experiencing seven to eight seconds of black screen after the BIOS check. That is, the computer was booting up, but the information scrolling down the screen couldn't be seen during that 7 or 8 second "blackout."
The boot up sequence appears to be back to "normal" with the 6.6 kernel series.
FWIW: The problem returned with the 6.6.17 kernel and continues with the 6.6.18 and 6.6.19 kernels.
Edit in: The "blackout" is now 9 seconds with the 6.6.20 kernel.
Last edited by cwizardone; 03-02-2024 at 03:22 PM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,125
Original Poster
Rep:
Year 2024, Round 14
Another batch of updates has been scheduled for release on Wednesday, 6 March 2024, at approximately 21:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on day (depending on your time zone).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
only 6.7.y maybe whole 6.x.x or even earlier.
