As a managed service provider (MSP) we’re using an off the shelf remote monitoring and management (RMM) platform. Recently, and just for curiosity’s sake, I decided to take a closer look at the Linux agent offered by this platform. I’ll admit to being somewhat shell-shocked when I discovered that the installer had Slackware Linux on the list of supported distributions.
After the Slackware Patreon page was initially discovered in mid-June 2019, it has been the source of quite a bit of debate regarding its authenticity. Anyhow, with that question out of the way, the bigger question now is whether there is still enough interest in Slackware Linux to make it a sustainable business for Mr. Volkerding.
A while back I lost access to the email address with which I had subscribed to the slackware-security mailing list. This does not please Bob, so today I logged into my webmail account and sent along a new request to join slackware-security and slackware-announce. The response I got in return gave me a good laugh and a swift feel of nostalgia.
Shortly following the distribution’s 25th year anniversary, Slackware maintainer Patrick Volkerding has shared some insight into his current financial situation and the issues he’s facing due to a lack of revenue from the Slackware store. According to Volkerding, the store has not forwarded any founds from sales or donations for the past two years.
There has been a long and tedious debate among slackers over whether the distribution should stick with KDE4 or move to Plasma 5. According to Slackware’s KDE maintainer Eric Hameleers, a decision has been made and Slackware 15.0 will ship Plasma 5.
So you’ve patiently been waiting for the next Slackware release but eventually you’re considering making the move to Slackware-current. So what exactly is Slackware-current and what would be the pros and cons of switching from stable to -current.
So the annual “Slackware needs PAM and Kerberos” thread is going strong over at linuxquestions.org at the moment. This particular topic always seem to awaken a collective inferiority complex within the Slackware community, where users are aggressively refuting any claim that Slackware is not a viable choice for business use (you can do anything with some lines of bash right?…). At the opposite side you have users arguing that Slackware has become a niche hobbyist distribution due to its reluctance to implement mainstream technologies.
My office workstation recently went trough a Slackware release upgrade by following the excellent systemupgrade article from the Slackware Documentation Project. Personally I experienced a few snags along the way so I’ll add a few notes for future reference.
Dlackware is not your average “GNOME for Slackware” project but instead aims to take the slack out of Slackware. What you get in return is the latest in “enterprise” technology. Dlackware delivers a fully functional GNOME 3.22 desktop with PAM, Wayland and systemd.
With all the noise lately about Dirty COW (CVE-2016-5195) and the lack of patched kernels from Slackware’s “Benevolent Dictator for Life”, I decided it was time to roll up the sleeves and get it done. Since Slackware doesn’t have a “sophisticated” build system and all that grease, it’s a trivial matter to step up to the plate and take responsibility for your own system. I’ll be using “vanilla-kernelversion” as my tag for the kernel and initrd. Also notice that I build my kernels as a normal user.