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.
Tue Nov 9 03:20:45 UTC 2021
ap/texinfo-6.8-x86_64-3.txz: Rebuilt.
Patched to fix issues with pt_BR locale. Thanks to Luiz Ramos.
l/harfbuzz-3.1.1-x86_64-1.txz: Upgraded.
l/netpbm-10.96.03-x86_64-1.txz: Upgraded.
l/qtkeychain-0.13.1-x86_64-1.txz: Upgraded.
n/iw-5.16-x86_64-1.txz: Upgraded.
n/postfix-3.6.3-x86_64-1.txz: Upgraded.
source/installer
Code:
Sun Nov 7 06:11:40 UTC 2021
usr/lib/setup/setup: Added 'power off' to the list of available options
('reboot' and 'shell'), when the installer completes successfully.
Sun Nov 7 06:11:40 UTC 2021
usr/lib/setup/setup: Added 'power off' to the list of available options
('reboot' and 'shell'), when the installer completes successfully.
I'm curious to know how many people won't be excited to reboot on their fresh new install of Slackware and just shut it down
I'm curious to know how many people won't be excited to reboot on their fresh new install of Slackware and just shut it down
Yeah, kind of wondering the same. Even when I install a fresh new virtual machine, I usually reboot just to make sure it does that successfully, then shut it down.
I'm curious to know how many people won't be excited to reboot on their fresh new install of Slackware and just shut it down
The humour is not lost on me, but perhaps in some cases to shut down and connect the disk to another controller, once the install has completed?
It doesn't really matter that much, you can unmount filesystems and just kill the power at that point, but it's good to have the option for when someone wants to shut down to mess with hardware before booting the installed kernel proper.
53 updates. Including a (* Security fix *)! : 51 upgraded, 1 rebuilt, 1 added
Code:
Tue Nov 9 20:22:27 UTC 2021
a/dialog-1.3_20211107-x86_64-1.txz: Upgraded.
ap/mariadb-10.5.13-x86_64-1.txz: Upgraded.
This update fixes a security issue:
Easily exploitable vulnerability allows high privileged attacker with network
access via multiple protocols to compromise MariaDB Server. Successful
attacks of this vulnerability can result in unauthorized ability to cause a
hang or frequently repeatable crash (complete DOS) of MariaDB Server as well
as unauthorized update, insert or delete access to some of MariaDB Server
accessible data.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-35604
(* Security fix *)
kde/bluedevil-5.23.3-x86_64-1.txz: Upgraded.
kde/breeze-5.23.3-x86_64-1.txz: Upgraded.
kde/breeze-grub-5.23.3-x86_64-1.txz: Upgraded.
kde/breeze-gtk-5.23.3-x86_64-1.txz: Upgraded.
kde/drkonqi-5.23.3-x86_64-1.txz: Upgraded.
kde/kactivitymanagerd-5.23.3-x86_64-1.txz: Upgraded.
kde/kde-cli-tools-5.23.3-x86_64-1.txz: Upgraded.
kde/kde-gtk-config-5.23.3-x86_64-1.txz: Upgraded.
kde/kdecoration-5.23.3-x86_64-1.txz: Upgraded.
kde/kdeplasma-addons-5.23.3-x86_64-1.txz: Upgraded.
kde/kdev-python-5.6.2-x86_64-4.txz: Added.
kde/kgamma5-5.23.3-x86_64-1.txz: Upgraded.
kde/khotkeys-5.23.3-x86_64-1.txz: Upgraded.
kde/kinfocenter-5.23.3-x86_64-1.txz: Upgraded.
kde/kmenuedit-5.23.3-x86_64-1.txz: Upgraded.
kde/kscreen-5.23.3-x86_64-1.txz: Upgraded.
kde/kscreenlocker-5.23.3-x86_64-1.txz: Upgraded.
kde/ksshaskpass-5.23.3-x86_64-1.txz: Upgraded.
kde/ksystemstats-5.23.3-x86_64-1.txz: Upgraded.
kde/kwallet-pam-5.23.3-x86_64-1.txz: Upgraded.
kde/kwayland-integration-5.23.3-x86_64-1.txz: Upgraded.
kde/kwayland-server-5.23.3-x86_64-1.txz: Upgraded.
kde/kwin-5.23.3-x86_64-1.txz: Upgraded.
kde/kwrited-5.23.3-x86_64-1.txz: Upgraded.
kde/layer-shell-qt-5.23.3-x86_64-1.txz: Upgraded.
kde/libkscreen-5.23.3-x86_64-1.txz: Upgraded.
kde/libksysguard-5.23.3-x86_64-1.txz: Upgraded.
kde/milou-5.23.3-x86_64-1.txz: Upgraded.
kde/oxygen-5.23.3-x86_64-1.txz: Upgraded.
kde/plasma-browser-integration-5.23.3-x86_64-1.txz: Upgraded.
kde/plasma-desktop-5.23.3-x86_64-1.txz: Upgraded.
kde/plasma-disks-5.23.3-x86_64-1.txz: Upgraded.
kde/plasma-firewall-5.23.3-x86_64-1.txz: Upgraded.
kde/plasma-integration-5.23.3-x86_64-1.txz: Upgraded.
kde/plasma-nm-5.23.3-x86_64-1.txz: Upgraded.
kde/plasma-pa-5.23.3-x86_64-1.txz: Upgraded.
kde/plasma-sdk-5.23.3-x86_64-1.txz: Upgraded.
kde/plasma-systemmonitor-5.23.3-x86_64-1.txz: Upgraded.
kde/plasma-vault-5.23.3-x86_64-1.txz: Upgraded.
kde/plasma-workspace-5.23.3-x86_64-1.txz: Upgraded.
kde/plasma-workspace-wallpapers-5.23.3-x86_64-1.txz: Upgraded.
kde/polkit-kde-agent-1-5.23.3-x86_64-1.txz: Upgraded.
kde/powerdevil-5.23.3-x86_64-1.txz: Upgraded.
kde/qqc2-breeze-style-5.23.3-x86_64-1.txz: Upgraded.
kde/sddm-kcm-5.23.3-x86_64-1.txz: Upgraded.
kde/systemsettings-5.23.3-x86_64-1.txz: Upgraded.
kde/xdg-desktop-portal-kde-5.23.3-x86_64-1.txz: Upgraded.
l/libxml2-2.9.12-x86_64-5.txz: Rebuilt.
Applied upstream patch:
[PATCH] Work around lxml API abuse.
Thanks to brobr.
x/libdrm-2.4.108-x86_64-1.txz: Upgraded.
x/libevdev-1.12.0-x86_64-1.txz: Upgraded.
xap/xsnow-3.3.2-x86_64-1.txz: Upgraded.
Just in time for tomorrow night here in Minnesota. :-)
Like a hamster in a mill... The mill is -current. Finding the hamster's name is left to the reader as an exercise. The real question is "when will the mill stop"?
Last edited by Didier Spaier; 11-09-2021 at 03:57 PM.
Like a hamster in a mill... The mill is -current. Finding the hamster's name is left to the reader as an exercise. The real question is "when will the mill stop"?
Probably, soon...
Our BDFL said that the kernel 5.15.x will be one shipped by release, the Plasma5 and XFCE looks being on a excellent shape, all looks being set - at least for me, what we run is basically RC2 as stability.
I believe that on the end of December or January we will have the release.
Our BDFL said that the kernel 5.15.x will be one shipped by release, the Plasma5 and XFCE looks being on a excellent shape, all looks being set - at least for me, what we run is basically RC2 as stability.
I believe that on the end of December or January we will have the release.
Agreed. I enjoy the speculation too. Christmas for 15.0 looks good to me. Back on topic. Thanks for the updates today, Mr. Volkerding. Current is looking polished to me.
Like a hamster in a mill... The mill is -current. Finding the hamster's name is left to the reader as an exercise. The real question is "when will the mill stop"?
Stop blaming the distro maintainers.
In my personal opinion the problem is with the upstream projects who are continuously "releasing" stuff (quotes are intentional).
In a distant past we had two, three maybe four proper high quality releases per year.
Now we get low quality "releases" every two weeks. And the "version" numbers that come with it are completely meaningless.
I very much appreciate the effort by Pat Volkerding trying to release a stable high quality Slackware 15.0.
In my personal opinion the problem is with the upstream projects who are continuously "releasing" stuff (quotes are intentional).
In a distant past we had two, three maybe four proper high quality releases per year.
Now we get low quality "releases" every two weeks. And the "version" numbers that come with it are completely meaningless.
I very much appreciate the effort by Pat Volkerding trying to release a stable high quality Slackware 15.0.
I wouldn't even blame it fully on the upstream projects. Both proprietary software and open source software is guilty of this and it's a byproduct of the general public demanding more software releases at quicker intervals. It's just the current times we live in to where people want their shiny new stuff now and not later.
I wouldn't even blame it fully on the upstream projects. Both proprietary software and open source software is guilty of this and it's a byproduct of the general public demanding more software releases at quicker intervals. It's just the current times we live in to where people want their shiny new stuff now and not later.
Yes, the end-user definitely has unreasonable expectations.
However, as a developer you have a choice. Sometimes you need to look the user in the eye and tell them that what they want isn't going to make their life better. This is common practice in the tech support world but most developers consider themselves to be above such menial labor and treat support techs like the school janitor.
User: My computer is broken, USB devices aren't showing up properly
Me: Looks like you have Fast Start enabled, let's turn that off
User: Fast Start? Doesn't that make my computer boot faster? I want that enabled...
Me: Well let's disable it for now and see if that solves problems with your USB devices. We can always turn it back on later. - 3 reboots later -
User: WTF it fixed the problem?? How does that even happen? Doesn't Microsoft have developers who can fix this?
Me: .... welcome to my world.....
I also have stories about MacOS destroying partition tables and the Ubuntu Wifi scanner crashing when too many SSID's are in the area. Devs had a choice and I think they chose wrong. But ultimately this is all off-topic flame war bait.
The rules clearly invites anyone to open new threads...
"When posting in an existing thread, ensure that what you're posting is on-topic and relevant to the thread. If the content of your post will interfere with the current discussion, you should start a new thread."
Surely we don't need moderators or management...
Hmmm... okay. Right. Sometimes we *really* do!
Thank you all for trying to remember this for the next few times
6 updates. Including a (* Security fix *)! : 6 upgraded
Code:
Wed Nov 10 20:32:37 UTC 2021
d/python3-3.9.8-x86_64-1.txz: Upgraded.
l/libtasn1-4.18.0-x86_64-1.txz: Upgraded.
n/curl-7.80.0-x86_64-1.txz: Upgraded.
n/ethtool-5.15-x86_64-1.txz: Upgraded.
n/samba-4.15.2-x86_64-1.txz: Upgraded.
This is a security release in order to address the following defects:
SMB1 client connections can be downgraded to plaintext authentication.
A user on the domain can become root on domain members.
Samba AD DC did not correctly sandbox Kerberos tickets issued by an RODC.
Samba AD DC did not always rely on the SID and PAC in Kerberos tickets.
Kerberos acceptors need easy access to stable AD identifiers (eg objectSid).
Samba AD DC did not do suffienct access and conformance checking of data
stored.
Use after free in Samba AD DC RPC server.
Subsequent DCE/RPC fragment injection vulnerability.
For more information, see:
https://www.samba.org/samba/security/CVE-2016-2124.html
https://www.samba.org/samba/security/CVE-2020-25717.html
^^ (PLEASE READ! There are important behaviour changes described)
https://www.samba.org/samba/security/CVE-2020-25718.html
https://www.samba.org/samba/security/CVE-2020-25719.html
https://www.samba.org/samba/security/CVE-2020-25721.html
https://www.samba.org/samba/security/CVE-2020-25722.html
https://www.samba.org/samba/security/CVE-2021-3738.html
https://www.samba.org/samba/security/CVE-2021-23192.html
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2124
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25717
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25718
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25719
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25721
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25722
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3738
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23192
(* Security fix *)
x/xorg-server-xwayland-21.1.3-x86_64-1.txz: Upgraded.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
