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.
In the -current logfile I see only four filenames with the "-15.0-" character string in it. Three first appear in 2017/Nov., and the other in 2018/June. As of the end of Nov/25, no new 15.0 filenames have been published.
For what it's worth, there are ever more "15.0" packages in current dudes!
Which new ones do you see then?
In the ChangeLog of Tue Nov 26 20:04:41 UTC 2019 I can find only
pkgtools (currently at build 28)
network-scripts (9)
aaa_elflibs (16)
and etc (10)
and all of them have been there quite some time already.
Both pkgtools and aaa_elflibs had some recent changes, but they are not newly re-versioned as 15.0 (they were upgraded to the 15.0 version with the -1 build):
Code:
Mon Jun 18 06:19:23 UTC 2018
a/aaa_elflibs-15.0-i586-1.txz: Upgraded.
Fri Nov 17 00:56:25 UTC 2017
a/etc-15.0-i586-1.txz: Upgraded.
a/pkgtools-15.0-noarch-1.txz: Upgraded.
n/network-scripts-15.0-noarch-1.txz: Upgraded.
(other upgrades on those dates removed).
Last edited by ehartman; 11-26-2019 at 03:00 PM.
Reason: Adding ChangeLog entries
People are just getting excited about the fact that something could be happening with a 15.0 beta soon after all indications are that 5.4.x will be the 15.0 kernel.
When I say "all indications", I mean:
- the kernel rc's were dropped into /testing when the rc's for 4.14 and 4.19 weren't;
- 4.14 and 4.19 were both released into -current main when they hit .0, which is not the case with 5.4.0, which is still in /testing;
- Pat seems to be being awfully cautious with this kernel, especially since he likes "to get everything just exactly perfect";
- it's been a damn long time since 14.2 by everyone's standards.
The only other possibility would be to wait till 5.9 [another year or so from now, and we don't even know if it'll be an LTS], but I think pretty much anyone would agree that that's entirely pointless.
Last edited by Lysander666; 11-26-2019 at 03:08 PM.
The aces are actually crawling up and down my sleeve. But it is very likely that 15.0 will release with an LTS kernel - I'd say 99.9% likely.
Certainly, and since 5.4 is slated as LTS as soon as the first 5.4 point release comes out, --Current will probably follow suite and officially jump to 5.4.
Certainly, and since 5.4 is slated as LTS as soon as the first 5.4 point release comes out, --Current will probably follow suite and officially jump to 5.4.
Agreed. I don’t know that to be true, but, that looks like a real possibility.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,152
Rep:
Quote:
Originally Posted by Jeebizz
Certainly, and since 5.4 is slated as LTS as soon as the first 5.4 point release comes....
Already done:
Quote:
Longterm
There are usually several "longterm maintenance" kernel releases provided for the purposes of backporting bugfixes for older kernel trees. Only important bugfixes are applied to such kernels and they don't usually see very frequent releases, especially for older trees.
Well there is still about 2 years to go before EOL of the 4.4 kernel which is the one that Slack 14.2 uses. So Pat can say that the kernel in the latest Slackware is supported until Feb.2022 and till then he has still time to cook the next version. However 5.4 will only be supported until Dec 2021. So thats sooner 4.4 in Slack 14.2
Well there is still about 2 years to go before EOL of the 4.4 kernel which is the one that Slack 14.2 uses. So Pat can say that the kernel in the latest Slackware is supported until Feb.2022 and till then he has still time to cook the next version. However 5.4 will only be supported until Dec 2021. So thats sooner 4.4 in Slack 14.2
There could be a chance that 5.4 might get an extension though? EOL dates for the kernel aren't always set in stone.
Well there is still about 2 years to go before EOL of the 4.4 kernel which is the one that Slack 14.2 uses. So Pat can say that the kernel in the latest Slackware is supported until Feb.2022 and till then he has still time to cook the next version. However 5.4 will only be supported until Dec 2021. So thats sooner 4.4 in Slack 14.2
This has been covered quite a few times in the forum, but the extended LTS kernels are a new thing. They didn't exist when 14.2 was released, so Pat expected to have 2 years of support for 4.4. We got lucky and, under pressure from Google (for Android), the kernel devs decided to selectively support certain kernels for 6 years instead of 2. They announced it with 4.4, then released the 4.9 with 2 years of support, which was later extended to 6. Then they released the 4.14 with 2 years of support, which was later extended to 6. The same could happen with the 4.19 and 5.4 kernels.
Pat may have decided to extend this development cycle because the kernel ended up receiving 6 years of support, or it just happened this way and we could've ended up with this extended development cycle even if the kernel only had 2 years of support.
But there's a lot of software in 14.2 that is effectively EOL, including KDE. That hasn't stopped Pat from having an extended development cycle, and there's nothing official saying an EOL kernel would've prompted any changes in support for 14.2.
One might say that 14.2, the best Slackware yet was so much more best that it takes quite a while of development upstream, downstream and all over the place to best it over again.
Judging of which, we are not only getting the very next Slackware yet, but the very best of the best Slackwares yet.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
, let's hope soon this big (and ours 
) wait is over...
