Three weeks ago, the quarterly (security and stability) updates to various Java source code repositories were released. This means, new packages for OpenJDK versions 8, 11 and 17 are now in my Slackware repository. It took a while but hey, here they are.
For OpenJDK 8 I still use icedtea to compile the Java sources because it is convenient. The more modern
Chromium update fixes 5th zero-day exploit for 2024
In Google's release notes for the latest Chromium 124.0.6367.201 source code it is mentioned that this release fixes a zero-day vulnerability. Beware: this is already the 5th zero-day which was reported and fixed in Chromium in 2024.
This vulnerability is already actively exploited in the wi
And here is more I learned on the same subject: 'lock' is not implemented under Ubuntu or #slackware so 'tmux lockc' does not seem to work either. The utility 'vlock' does the same thing, but is not installed by default.
But installing 'vlock' does not make 'tmux lockc' work under Linux. ☹️
Under #OpenBSD and #NetBSD 'lock -p' uses your default password, but 'tmux lockc' work as expected (meaning, it asks for your login password). No '-p' means entering a separate password for unlocking.
Last I tried screwing around with #zfs, #KVM and #qemu on #slackware I had a bunch of fun with scripts from sbo and dependency hell – since neither is an official slack package.
How does this fare in 2024 if I were to try to get a headless host for my stuff (qubes-like but I like pain)?
Thanks! I'm torn between my current #gentoo and #slackware as a minimal headless host I can host (paravirtualized?) VMs on, like a #devuan desktop, old Windows and perhaps trying different archs.
With systemd now poised to replace sudo as well I can't help but be a little bitter about the way in which the concerns about systemd being an ever-scope-creeping behemoth of attack surface area controlled by one (admittedly rather unpleasant) person were swept to the margins and everyone pushed forward with it like nobody cared, and now our modern Linux distro choices just treat it like an inevitability and there's not a damn thing anyone can do about it because it was "already decided" years ago
Apparently it was possible to do a "CD-ROM” install of #Slackware which would install a minimal system to the hard disk, and run most of the system from the CD. I wonder if anyone actually ran their system like this. #retrocomputing
This is why #Slackware is a bit like the BSD of Linux: it simply works, does not have any cruft (coughcough systemd cough) and is still wonderfully usable.
It is fairly open, easy to understand with its shell scripts for everything, KISS attitude. And it keeps on running with a minimum of maintenance.
I also refreshed what I’m calling the “pkg_dump” of #slackware#aarch64 package builds yesterday. There’s a shit-ton of stuff there, like a full gnome 46 desktop, and the latest Firefox 125.0.1, MAME, i3, sway, hyprland, etc. https://slackware.lngn.net/pub/aarch64/pkg_dump/