LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-19-2021, 12:07 PM   #61
GazL
LQ Veteran
 
Registered: May 2008
Posts: 6,882

Rep: Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988

re the issue I referred to: yes, dev's were aware and even provided fixes in a private branch, but for whatever reason, chose not to merge them into 5.4 LTS. Anyway, it was just one example to make the point that *stuff* happens, and LTS aren't immune.

Quote:
Originally Posted by bassmadrigal View Post
Again, nobody is saying that the LTS kernels are perfect, but once released, they're more predictable than a new stable kernel release...
And that is the point on which you and I fundamentally disagree. My view is that they're all pretty much a crapshoot.
 
Old 05-19-2021, 12:20 PM   #62
cynwulf
Senior Member
 
Registered: Apr 2005
Posts: 2,727

Rep: Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367
They're only predictable on the server hardware / vms on which they were tested... for any other user they're a complete unknown. You be one version of the driver version which fixes you particular problem and that may never make it as a backport to the LTS.
 
Old 05-19-2021, 01:01 PM   #63
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656
Quote:
Originally Posted by cynwulf View Post
bassmadrigal: My point is that before the LTS kernels, Slackware managed to thrive and survive without them. With the LTS kernel, the distribution maintainer still has to rebuild binary packages every patch...
But in that golden time before LTS kernels "dirtied" Slackware, Slackware never pushed a new major kernel release into a stable release of Slackware since 9.1 (and that was a 2.4.x kernel). So, if you stick with the status quo there, then we would be stuck with a kernel with no updates beyond what was shipped within months of a stable release and it would be EOL within months. Slackware also had much more frequent releases, so sticking with a single kernel for less than a year was not nearly as big of a deal as it is compared to now when releases are multiple years apart.

Quote:
Originally Posted by cynwulf View Post
I personally think a known working good stable kernel is the best starting point then moving up to an LTS only once it's established to be a good release. As it stands I recall LTS kernels which were not good releases (unless perhaps you were Red Hat), gave users a lot of grief with hardware support, etc.
If you started with a stable release and then "moved up" to an LTS release once established as good, then you'd either be sitting on an EOL kernel for up to a year until the next LTS kernel is released and verified stable or backtracking to a previous LTS kernel and would lose hardware support.

Determining stability is something that -current is used for. 5.10 started off rough (just like 4.14), but it has stabilized for most users (just like 4.14 did before -current moved to 4.19). The 4.4 kernel was introduced into 14.2's -current 3 days after release. It stayed in -current for the next 5 months until 14.2 was released. 14.2's -current was used to determine the stability of that kernel before releasing 14.2 stable.
 
1 members found this post helpful.
Old 05-19-2021, 03:29 PM   #64
Jan K.
Member
 
Registered: Apr 2019
Location: Esbjerg
Distribution: Windows 7...
Posts: 762

Rep: Reputation: 487Reputation: 487Reputation: 487Reputation: 487Reputation: 487
Red face Luckily we are in safe hands...

And funny enough I somehow both understand and agree with everyone's opinions!

But no matter what 15 ends up with, it will make no difference.

You still only have two choices: follow Pat's offerings or roll your own...


I can guess what Pat will serve us but as said; imho it really won't make any difference.
 
1 members found this post helpful.
Old 05-19-2021, 04:09 PM   #65
dr.s
Member
 
Registered: Feb 2010
Distribution: Slackware64-current
Posts: 338

Rep: Reputation: 156Reputation: 156
Quote:
Originally Posted by Jan K. View Post
And funny enough I somehow both understand and agree with everyone's opinions!
...
They boil down to "predictable crap" vs. "unpredictable crap", I'll put my money on predictable
 
1 members found this post helpful.
Old 05-19-2021, 04:34 PM   #66
ttk
Senior Member
 
Registered: May 2012
Location: Sebastopol, CA
Distribution: Slackware64
Posts: 1,038
Blog Entries: 27

Rep: Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484
Programming for 43 years has taught me that the number of bugs introduced by code changes are proportional to the size of a change times its complexity, but I don't expect that to change anyone's mind.

At the end of the day, it's like what Jan K said -- we can use what Pat provides, or roll our own.

I expect to be using Pat's kernels for my use-cases, but to each their own. My priorities and yours don't have to align.
 
1 members found this post helpful.
Old 06-27-2021, 01:30 PM   #67
dfwrider
Member
 
Registered: Feb 2010
Location: San Antonio, Texas, USA
Distribution: Slackware
Posts: 43

Rep: Reputation: 34
My 2 cents: I tend to view a Slackware "release" as comparable to RHEL, and "current" as comparable to Fedora. Slackware of course being superior on both account of course. Anyway, I prefer maximum stability/predictability in a Slackware release. I can then tweak it as I require, including replacing the kernel. If I need something more current out of the box, then I use Current.

Q: Will putting an LTS kernel in 15, delay it?
 
1 members found this post helpful.
Old 06-27-2021, 01:44 PM   #68
cwizardone
LQ Veteran
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,041

Rep: Reputation: 7219Reputation: 7219Reputation: 7219Reputation: 7219Reputation: 7219Reputation: 7219Reputation: 7219Reputation: 7219Reputation: 7219Reputation: 7219Reputation: 7219
Quote:
Originally Posted by dfwrider View Post
.......
Q: Will putting an LTS kernel in 15, delay it?
You might want to read the 7 June 2021, change log entry,

http://slackware.oregonstate.edu/sla.../ChangeLog.txt

Last edited by cwizardone; 06-27-2021 at 01:46 PM.
 
3 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: The LTS Linux Kernel 5.10 To Be Maintained For Only 2 Years If Companies Don’t Help Support It LXer Syndicated Linux News 0 01-30-2021 08:26 PM
LXer: Upcoming Linux 5.10 release will love you longterm, pushing support out to 2026 LXer Syndicated Linux News 0 10-28-2020 01:30 AM
[SOLVED] How do I analyse a kernel segfault sh[2026] error ? bugrake Linux - Server 3 12-21-2014 12:31 AM
ERROR 2026 (HY000): SSL connection error: SSL_CTX_set_default_verify_paths failed prw8864 Linux - Software 1 11-15-2014 09:24 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:13 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration