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.
nmcli: accept abbreviations for the UUID with the connection selector in `nmcli connection $operator uuid $uuid`.
nmtui now supports editing Wi-Fi WPA-Enterprise, Ethernet with 802.1X
authentication and MACsec connection profiles.
bond: add "balance-slb" option which implements source load balancing
with "balance-xor" mode and "vlan-srcmac" xmit_hash_policy. In this
mode, NetworkManager configures nftables to prevent loops in the
switch.
[ANNOUNCE] mesa 22.2.1
I'm a bit late getting this out, I blame XDC. Anyway. This is pretty
much what *should* have been in 22.21, with a few extras, so there will
be a regularly scheduled 22.2 release next week.
We've got lots of stuff here: llvmpipe, lavapipe, freedreno, aco, mesa,
turnip, virgl, r600, zink, radv, core gallium, and nir. All in all, lots
of good fixes all over the tree.
I am installing Slackware64-15.0 on another machine in order to do some testing. I haven't done it for a while. I was wondering why I have to install out of date packages just to update them using slackpkg a few minutes later. Is there a way around it? I don't think there is an option in Slackware installer to use /patches directory by default.
Would it be a good idea to just install newest kernel etc right away? Or at least if there was an option to do it?
Is there some rationale behind the current installer behaviour other then keeping it simple
I am installing Slackware64-15.0 on another machine in order to do some testing. I haven't done it for a while. I was wondering why I have to install out of date packages just to update them using slackpkg a few minutes later. Is there a way around it? I don't think there is an option in Slackware installer to use /patches directory by default.
Would it be a good idea to just install newest kernel etc right away? Or at least if there was an option to do it?
Is there some rationale behind the current installer behaviour other then keeping it simple
Regards,
Alex
You are not alone. There is a link in that thread to some patches that I have used.
I believe that's the time to jump ASAP to kernel 5.19.16 on -current and 5.15.74 on stable v15.0 because they fixes 5 (five) really nasty CVEs on WiFi management.
Thanks you!
Last edited by LuckyCyborg; 10-15-2022 at 06:40 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.