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.
My Raspberry Pi based hosting came to an abrupt end earlier this week as the RPi3 suddenly became unresponsive. Powering off and on the device resulted in an infinitive loop of I/O error messages. I’ve tried to recover the filesystem, but unfortunately my attempts proved to be unsuccessful.
To start the weekend off with a bang my Apache webserver failed to revive after the log rotation service had issued a restart. I’m hosting this website on a Raspberry Pi 3 so my first concern is always memory card corruption and data loss. Thankfully those fears turned out to be unfounded, but what actually went down?
From the httpd error_log:
I recently bought a new Raspberry Pi 3 and installed Slackware ARM current (hard float) on it. My goal was to compare the performance of the hard float port against Slackware ARM 14.2 (soft float), which is currently powering this RPi3 hosted website.
This website recently celebrated its second year of Raspberry Pi based hosting. It’s currently running on a RPi3 with Slackware ARM 14.2 (32-bit soft float). Somewhat to my surprise, the second year went by without a single glitch.