In the works: LibreOffice 24.2.0 for Slackware 15.0
Apart from post-COVID syndrome there were some other setbacks lately, but those were mostly software-centered. Like the fact that I can not build a 32bit Chromium package for instance.
But also the realization that the latest LibreOffice 24.2.0 can no longer be compiled on Slackware 15.0 - its gcc 11.2.0 c
013: SECURITY FIX: February 13, 2024 All architectures
DNSSEC protocol vulnerabilities have been discovered that render various DNSSEC validators victims of DoS while trying to validate specially crafted DNSSEC responses.
Fix CVE-2023-50387 and CVE-2023-50868 in unwind(8) and unbound(8).
I finally pushed a new #liveslak#slackware#nwgshell ISO today! A LOT has changed since the last one a month ago. @nwgpiotr has added a webkitgtk-based inline doc reader which also can read everything in /usr/doc, everything nwg-* has had updates, and I’ve even put sway v1.9-rc3 on the iso as my testing says it’s nice and stable. Enjoy! https://rekt.lngn.net/nwg/
So, @darth got me thinking... I have an old Phenom II X4 965 Black lying around. And I do have an old AM3 socket mobo, I also have an old case that is missing some screws. I might dig through my junk pile and build something. Use what I already have and only buy the parts I absolutely need.
I'm imagining maybe a #Slackware#linux server that is basically a hypervisor using #KVM and #Qemu that will run #BSD, #Arch, #RockyLinux, etc. basically all the POISX OSs I want to play around with.
I somehow avoided getting infected with COVID for all these past four years, but this week unexpectedly it hit me after all - and that while being inoculated multiple times. Oh well, they say that the inoculations keep the more severe symptoms at bay.
Still, this feels like a very bad flu, I have been in bed for two days, feeling delirious in the beginning but just nauseous and dizzy now, accompanied by t
@jjdavis
Oh my... memories
Yeah, coming from IDE drives with little to no space left I can attest to that for sure 😂
And floppies... oh boy... nostalgia all over 🙂
Friends look at me strange when doing full installs on everything... times changed. #Debian or #Slackware is a full install - period.
Drives are so cheap now.
❝Today, thanks to Android and ChromeOS, Linux is an important end-user operating system. But, before Linux, there were important Unix desktops, although most of them never made it. …❞
Chromium 121 for Slackware… don’t hold your breath
Chromium 121 sources were released yesterday, and as much as I would like to tell you that the Slackware packages are ready, in fact it appears that you will have to wait for them for an unspecified amount of time.
I found out that the build of Chromium now needs Google's custom ver
No matter how hard one tries, #Slackware truly is forever.
Some things simply are the way they are.
Mabye it sounds silly... but anytime I work with it, it puts a smile on my face 🙂
Keep collection slack and use #Slackware :slackware:
There is a reason why it still is very much alive and well 😎
Initial testing of the udevadm based system RAM report in #inxi / #pinxi are now running well. Most of the logic from dmidecode mapped pretty closely to the udevadm output, though the udevadm output requires one further processing step, but it's pretty similar.
This is a first, showing non root, non dmidecode based system RAM info.
There's one udevadm data glitch, it shows RAM module voltage as 1 always, which looks like a bug, so added a note about that if it's the case.
1/
Testing calls now out for #pinxi (next #inxi), it will be exciting to see if this one gets enthusiastic attention or not, in theory it should since this is one of the longest standing weak spots, not being able to get decent ram per stick and array data.
Getting testers used to be a lot easier, now it's hit and miss if a specific feature will catch anyone's attention. My bet is on #slackware forums, those guys tend to really like core hardware stuff, they were massive help for CPU refactor.
I’ve found a glibc/gettext bug on #slackware, I noticed last week or so on arm64 port, which now happened on x86 today to me. But diagnosing the issue is going to be a pain point, cuz who tf wants to mess with glibc? Anyway, now I’m messing with glibc. I’ll break all the things.