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.
Fri Sep 10 18:58:52 UTC 2021
a/grub-2.06-x86_64-4.txz: Rebuilt.
Install file in /etc/grub.d as .new so that they won't be clobbered by
future package updates.
Patch grub-mkconfig to skip .new files in /etc/grub.d.
Thanks to denydias.
d/bison-3.7.6-x86_64-1.txz: Upgraded.
Reverted bison-3.8 since it breaks building glibc. Looks like I picked the
wrong week to upgrade bison. ;-)
Thanks to nobodino.
l/jansson-2.14-x86_64-1.txz: Upgraded.
l/libcap-2.57-x86_64-1.txz: Upgraded.
l/liburing-2.1-x86_64-1.txz: Upgraded.
xap/libnma-1.8.32-x86_64-2.txz: Rebuilt.
Added glib-compile-schemas to the install script. Thanks to bormant.
xap/network-manager-applet-1.24.0-x86_64-2.txz: Rebuilt.
Removed glib-compile-schemas from the install script. Thanks to bormant.
Looks to me like Volkerding's mostly fixing problems as feedback trickles in from the community.
Debugging is the least predictable part of any project. I'm guessing we'll see more of the same until the problem reports stop arriving, then either another RC or a stable release.
As he said, we should end up with an LTS kernel
So we have to wait, most probably, for the 5.15 kernel
Which would be, at least, a very good timing
That's not how I interpreted the Changelog:
Code:
Mon Jun 7 18:53:49 UTC 2021
Hey folks! Sorry about the delay in getting this batch out but I had other
distractions going on here last week that prevented getting this one wrapped
up. Anyway, probably the highlight of this update set is that we've decided
to abandon the 5.10 LTS kernel in favor of following the latest one. We've
never really had a policy that required LTS in a stable release although that
is how it has been done for years, but based on comments from the Slackware
community it seems like 5.10 LTS isn't getting a lot of love and lacks
hardware support that people need now. Conversely, the reports on 5.12 have
been almost entirely positive, so we're going to provide what we think is the
best available kernel. It's unlikely that we'll see another LTS prior to
release, so the plan for maintenance is to keep following the latest kernels
as needed for security purposes. If that means we have to jump to a new branch
while supporting the stable release, we'll start the kernel out in testing
first until we've had some feedback that it's safe to move it to the patches
directory. Sooner or later we will end up on an LTS kernel again, and at that
point we'll just roll with that one. Feel free to comment (or complain) about
this plan on LQ... I'll be curious to see what people think. Anyway, enjoy!
In other words: Release 15.0, continue upgrading kernels until an LTS is released, then stick with it.
In case anyone's curious about wget2 features, according to https://en.wikipedia.org/wiki/Wget#Wget2 it offers http/2, http compression, parallel connections, if-modified-since support and tcp fast open.
In case anyone's curious about wget2 features, according to https://en.wikipedia.org/wiki/Wget#Wget2 it offers http/2, http compression, parallel connections, if-modified-since support and tcp fast open.
I assume parallel connections to one server, unlike aria2, which allows you to download, for example, an ISO from multiple servers in parallel, or am I wrong?
I assume parallel connections to one server, unlike aria2, which allows you to download, for example, an ISO from multiple servers in parallel, or am I wrong?
I assume this too.
And those parallel connections are today basically useless because the servers hate them and kicks you out.
As he said, we should end up with an LTS kernel
So we have to wait, most probably, for the 5.15 kernel
Which would be, at least, a very good timing
Sounds fair. But I would have expected a Release Candidate to have a freeze on newer developments such as an updated kernel and a concentration only on debugging existing features? Bear in mind as well that the RC 1 was declared about a month ago: Mon Aug 16.
In case anyone's curious about wget2 features, according to https://en.wikipedia.org/wiki/Wget#Wget2 it offers http/2, http compression, parallel connections, if-modified-since support and tcp fast open.
Can wget1 and wget2 coexist without collisions? Maybe we need to manually uninstall the first version? What's the point of having installed both versions?
A slackware forum thread dedicaced to the latest slackware-current changelog
This will at least give some visibility on the latest updates here on the forum
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
