After four months of hosting this WordPress blog on a RPi3 I have yet to experience a single issue. No filesystem errors, no kernel oops’s and no hard freezes. Definitely an enjoyable change of pace from the preceding twelve months of hosting this site on a Raspberry Pi 2.
I’ve not been doing any overclocking whatsoever on this device and I believe that to be the decisive factor when it comes to improved stability. My old RPi2 is pretty much useless at this point and I’m guessing it simply got burned out before its time. As for storage, I’m still using a SanDisk MicroSDHC Ultra UHS-I 32GB card.
I have also (at least for now) halted the process of moving this website to a cloud based VPS after learning that Slackware ARM is moving ahead with a hard float port.
Nor is there currently any indication that the support for Slackware ARM 14.2 (soft float) will be dropped any time soon.
Configuring and using a generic kernel on EFI-based platforms with ELILO is pretty much an identical exercise to using LILO with legacy systems. Slackware provides you with a mkinitrd generator script to assist in making an initrd image to boot your system.
As an example, on my system the generator script suggests the following mkinitrd command to build an initrd (initial ramdisk).
The rather excessive list of modules I got in return was a result of having a USB keyboard attached. I checked the script since it didn’t make any sense to me (based on the drivers I was using), and I noticed that the script will return a hard coded list of drivers if it detects an attached USB keyboard. Anyhow, since I didn’t need those drivers I simply used the following command to add support for the ext4 filsystem:
Please be aware that if you have an encrypted root partition you will have to add support for your USB keyboard. However, the ELILO menu still works without the drivers as it’s managed by the UEFI firmware at that point.
The next step is moving the initrd image and the generic kernel to the EFI partition. On my system the path is /boot/efi/EFI/Slackware/
When I began writing this review there had been 921 days since the last stable Slackware release. The apparent dormant state of development raised a few questions about the health of the distribution, but as usual the rumors of Slackware’s decline was greatly exaggerated. The following review is based on the Slackware 14.2 release candidates. Slackware 14.2 x86_64 has been installed and reviewed on a Asus ROG G771JM.
What’s new with Slackware Linux 14.2
Slackware 14.2 delivers incremental updates with KDE 4.14.21, XFCE 4.12 and Fluxbox 1.3.7. The Linux Kernel is at version 4.4.14 and the X Server checks in at version 1.18.3. Still, the most predominant change with Slackware 14.2 has probably been the replacement of ConsoleKit (user and session tracking) and udev (device manager). ConsoleKit and udev were merged into the systemd software suite which unfortunately left Slackware behind with older and unmaintained versions.
Thankfully new forks arrived to pick up the slack, and ConsoleKit2 and eudev were added as their replacements. If you were having sleepless nights filled with fear of Slackware abandoning its KISS policy then you can rest assured that it’s not happening anytime soon. Also making it first appearance in Slackware is PulseAudio which predictably didn’t get a warm embrace from the Slackware community.
I’m old not obsolete – Arnold Schwarzenegger in Terminator Genisys
Is Slackware still usable?
A full Slackware installation provides you with a modern and ready to use operating system. And before you ask, that does include desktop environments. On the surface, Slackware looks and behaves just like any other comparable Linux distribution.
What about the lack of automatic dependency resolution.
It’s true that Slackware doesn’t offer automatic dependency resolution but it’s important to acknowledge that there is no unmet dependencies on a full Slackware install. As for installing additional software, you do need to find and install additional dependencies manually. Slackbuilds.org which was recently endorsed by Patrick Volkerding provides build scripts for a variety of additional software currently not available from the official Slackware repository.
I believe the concept of manual dependency resolution might seem exhausting based on experiences with other distributions where installing software often starts a chain reaction of pulling additional packages.
As an example, on Debian based distributions installing packages with apt-get will by default install recommended packages as dependencies. If you want to install the command line tool youtube-dl, you’ll also get a video player, a toolkit for handling RTMP streams, ffmpeg and more multimedia codecs than you knew existed. This approach of installing everything and the kitchen sink has its merits but as far as youtube-dl is concerned, its only dependency is python.
Is Slackware ready for the masses?
I don’t see why not, the time and effort you invest to learn the basics of the system is paid back in full by giving you a stable and reliable platform for work or leisure. Obviously not everyone will appreciate the Slackware approach of putting the user in charge of the system, but I suspect many will if given the opportunity.
Slackware uses a ncurses based installer providing you with a simple text based installer. Perhaps the most difficult part of the installation for new users is the manual disk partitioning. If that is the case then you could always do the partitioning beforehand with Gparted or similar tools. I also recommend getting familiar with the install guide from the Slackware Documentation Project.
Pkgtool is a menu-driven package maintenance tool provided with the Slackware Linux distribution. It allows the user to install, remove, or view software packages through an interactive system. Pkgtool can also be used to re-run the menu-driven scripts normally executed at the end of a Slackware installation. Source: man pkgtool
Slackpkg is a tool for those who want to easily install or upgrade packages via the network. With slackpkg, you can have a minimal installation of Slackware Linux and install/upgrade only those packages you need the most.
Source: man slackpkg
Slackware is a multiusage distribution, it’s not tailored made for the desktop or server usage, but lets the user configure the system according to her needs.
At the office
I’m using Slackware on my office workstation running a full LAMP stack for development and sysadmin tasks. The only downtime I’ve ever experienced has been caused by power failures, though colleges have threatened to take the machine down due to excessive uptime bragging (they’re all running Windows obviously).
I would definitely recommend Slackware for server tasks. Slackware is simple, secure and rock solid. Those are features I greatly appreciate from a server installation. As a side note, you’re reading this review on a Raspberry Pi 3 powered by Slackware ARM.
On the modern laptop
Slackware 14.2 was my first Linux installation on UEFI based hardware and despite some initial fud regarding secure boot (which I’ve turned off), it does coexist happily with my Windows 10 installation. There is definitely no reason to cling to legacy bios and mbr as UEFI is the far better alternative in my opinion.
As for hardware compatibility, everything is working great with the latest 4.4.14 kernel. I did have some serious issues with the nouveau driver (hard freezes) on earlier versions of the 4.x kernel but those seemed to have been fixed upstream.
Slackware supports most media formats out of the box with few exceptions. However, if you want to enjoy your dvd collection you will have to install some additional codecs.
Look and feel
There is no theming or other distro specific customization with Slackware Linux. Everything is as close to the vanilla sources as possible.
With each release Slackware tries to stick with stable versions of all included software. This means that apart from bug and security fixes, you won’t get the latest version of any software without compiling and installing it yourself.
KISS (Keep it simple stupid):
When you dig below the surface you’ll find that Slackware is one of the few remaining Linux distributions that is still trying to offer a simple and configurable system. Editing plain text configuration files is still the way of Slack.
Write programs that do one thing and do it well, that is the Unix philosophy. Red Hat has deemed the ways of old as obsolete and outdated. Currently Slackware is one of few remaining distributions resisting the systemd assimilation.
No cloud integration:
The dark side clouds everything. With Slackware you don’t have to share your personal data with software giants in return for better personalized ads.
Slackware has a closed development model.
Lack of Kerberos and PAM:
I’ll leave it at that.
Those annual “is Slackware dead” threads could be avoided if a few updates came more frequently from Slackware HQ. Not everyone reads the Slackware-current changelog, and when the latest update on your commercial website was from 2013, well it’s not ideal me thinks.
Is Slackware still relevant in 2016?
Slackware offers an alternative to the widespread adaption of systemd that we have seen with most mainstream distributions. I’m all for supporting distributions that resist the weight and pressure Red Hat is throwing around with their aggressive push towards the systemd software suite. In 2016 we should be thankful that we still have a few alternatives preserving our freedom of choice, and that in my humble opinion makes Slackware Linux more relevant that ever.