SAIRPi Project - Slackware AI on Raspberry Pi
About Slackware
First and foremost, Slackware is a trademark of Patrick Volkerding.
Slackware is the longest-running, currently maintained, Linux distribution in existence. Slackware version 1.00 was first distributed to the public on 17 July 1993, at 00:16:36 UTC. Now 33 years 0 months and 28 days old, it remains the definitive UNIX-like experience. It predates Debian by two months and remains the most faithful to UNIX principles and traditions. By adhering to a strict KISS philosophy (Keep It Simple, Stupid), Slackware eschews flashy GUIs in favour of plain text files and shell scripts. It is a Linux distribution built on the rock-solid foundations of stability, reliability, security, and is a predictable powerhouse for those who prefer to truly own their operating system rather than just use it.
NB: It's important to state from the outset that what follows is strictly the opinion of the SAIRPi Project and not necessarily objective fact. However, after more than two decades of using Slackware, we have come to appreciate just how stable and reliable it is, and that it remains the only Linux distribution that offers users complete transparency and dominion over the system at every level. The lack of automated dependency resolution and 'magic' configuration layers is a practical choice that ensures the system is entirely predictable and under total control. Which is perfect for R&D activities and the work that we are involved in.
Why did we choose Slackware?
It may be a pertinent question for anyone outside the Slackware bubble, but for those who already know, the answer usually comes down to:
"Pragmatism, and absolute assurance of a secure, stable, reliable, and highly predictable operating system."
Another, more straight-forward, answer would be, "Because it does exactly what it’s designed to do, and does it flawlessly."
Slackware doesn’t have multiple layers of convoluted functionality, doesn’t hide what it’s doing, and doesn’t make decisions for you. It gives you a clean, stable system and expects you to know what you’re doing with it.
The Pragmatism - i.e. "Keep It Simple, Stupid" (KISS) principle:
KISS implies that simplicity should be a design goal, and with Slackware that's exactly what you get.
Slackware doesn't try to be smart. It never tries to out-class or second-guess the user. The user is always in control and nothing unexpected or unseen happens without the user being aware of it.
Slackware, although not designed to be - but by the very nature of its design, is the best teacher out of all available Linux distributions. It expects users to know what they're doing, and, in-turn, if/when they don't they'll go off and acquire the knowledge. This is how Slackware works, and users gain an insight, and an education, just by using the system. This often requires a lot more time and effort to learn about the system and its mechanics/dynamics. Which is very rewarding in terms of hands-on knowledge and first-hand experience.
Slackware is "vanilla software" so you get the software exactly how the developers intended, not a heavily patched version customised by a distro maintainer.
Configuration is done via simple scripts and plain text files. If/when you break something, you know exactly where to look because there aren't five layers of abstraction obfuscating the problem.
The vanilla software aspect is particularly overlooked. When you learn a process or application on Slackware, you're learning the software itself, not the distro-specific way of handling it. It makes you a better Linux user overall because the knowledge and skills gained by using Slackware are transferable to almost any UNIX-like environment.
But... WHY use Slackware when there are easier options?
To answer "Why Slackware?" for SAIRPi, you have to look into and appreciate the intersection of old-school stability and cutting-edge, state-of-the-art technology. Besides this, it's the ultimate operating system for a Raspberry Pi, and always has been.
While the tech world is obsessed with new, convenient, automated, and abstracted, we chose Slackware because it is recognised as the most reliable and predicatble Linux distribution, founded on principles of stability, simplicity, and a UNIX traditions.
We know what Slackware is capable of, and how it works flawlessly in every instance and at every level. It has a renowned history and a fully documented, prestigious, and long-standing lineage.
Slackware has remained a completely independent project throughout its history, operating outside the influence of major corporate Linux entities. Its core strengths lie in its transparency, lack of unnecessary automation, and dedication to providing a vanilla (unpatched) software experience.
Unlike nearly all modern Linux distributions, Slackware does not automatically handle dependencies, which means no circular dependency nightmares and any third-party software or automated tools that may have been installed are less likely to break the system.
Slackware is proven, predictable, ultimately reliable, and completely under the user's control. For these reasons, and many more, Slackware is unabridged and remains peerless. This is exactly what the SAIRPi Project needs and why Slackware was the only viable OS option over all other options and alternatives.
1. Ultimate stability, reliability, and predictability
Slackware is renowned for being rock solid. It avoids bleeding-edge software, preferring to release packages that have been thoroughly tested, making it an excellent choice for servers, production workstations, and test-rig setups.
2. Adherence to the KISS principle
Slackware follows the Keep It Simple, Stupid (KISS) principle, which emphasises simplicity in design and operation. The OS is not overly complicated. It doesn't contain multiple layers of hidden complex applications for automation or otherwise. It's proven software that's transparent and highly conservative. Slackware’s KISS principle makes it the ultimate choice for users who want a reliable, bare metal Unix-like experience that puts them in complete control, rather than a system that makes decisions for them.
3. Transparency and control over magic
In most modern distributions, a simple update can trigger a cascade of automated scripts that change your configuration without your consent. In AI development, where library versions (Python, CUDA, C++ compilers) are critical, you can't afford magic. Slackware doesn't do anything behind your back. If a config change happens, it's because you made it or at least allowed it via slackpkg *.new files. Because Slackware does not use automatic dependency resolution or heavy graphical configuration tools, it forces users to understand how the operating system works, offering unparalleled control.
4. Vanilla software
Slackware ships software as close to the original author's intent as possible, avoiding heavy, distribution-specific patches. This reduces bugs and ensures compatibility.
5. Highly customisable
While Slackware offers a complete, functional system out-of-the-box, it's designed for manual configuration via plain text files. The lack of abstraction allows users to easily tune the operating system to their specific requirements, maximising performance.
6. THE BEST Linux learning tool
Slackware is widely considered as one of the best distributions for learning the inner workings of Linux. No other Linux distribution can teach you about your operating system like Slackware can. One of the advantages is that once you learn the fundamental ways of how your Slackware operating system works, it's transferable skills and knowledge. Meaning you'll be able to understand how other Linux-based operating systems work much easier.
7. Optimised for efficiency
Lacking bloat and unnecessary background services, Slackware is highly efficient and performs admirably on both modern and older hardware. Slackware is fast because it keeps things simple, providing a stable, predictable, and uncluttered foundation, rather than a flashy or heavily automated experience.
8. No systemd
Slackware continues to use traditional SysVinit / BSD-style init scripts rather than systemd, which is preferred for its simplicity and traditional UNIX-like design.
9. Simple package building and management
Slackware comes complete with build scripts for all its packages, and then some. Through websites like SlackBuilds.org, users have access to a large repository of scripts that make it easy to compile and install custom software from source, adhering to the first-class citizen philosophy of locally built packages.
With Slackware there is no automated package dependency resolution by default. While often seen as a disadvantage, this approach means the package manager does not spend time resolving complex dependency chains and/or installing GBs of software packages with each update. The advantage is that the user knows exactly what is installed on their system at any given time.
10. Performance premium
Slackware isn't recklessly extravagant with resources like many modern Linux distributions seem to be. This gives it the edge on performance and system architecture. Why waste RAM on a D-Bus nightmare or a dozen background helper daemons (if you're lucky) that you didn't ask for or need? Slackware is legendary for its small footprint and minimal overhead, shipping with a minimal set of running services by default. With fewer background processes and daemons running, more CPU cycles and RAM are available for the user's workload.
11. Predictability and longevity
Slackware is an operating system that doesn't change unexpectedly, with simple package management and predictable updates, offering long-term stability and reliability. For example: you don't want your Edge AI node to break because a package manager decided to helpfully upgrade a core system component mid-inference. Slackware's conservative approach to package management means that once your system is configured, it stays that way. Period. It boasts a "set and forget" foundation built on "configure and know".
12. Ease of use, maintenance, and troubleshooting
By following The Slackware Way, you actually learn how to use your system and maintain it. When you're troubleshooting an elusive problem, knowing exactly how your OS is layered - from the kernel up - isn't just a bonus, it's a massive technical advantage.
" Use Debian and learn Debian. Use Ubuntu and learn Ubuntu. Use Slackware and learn Linux! " - an Internet aphorism.
Slackware has the only installer that makes you feel like you've actually earned your operating system. 🐧
Support for Slackware Linux
It's always worth bearing in mind that the Slackware Linux project is funded entirely through donations. If you'd like to show your appreciation, and/or to support the development of Slackware, you're able to do so directly via Patrick Volkerding on PayPal and Slackware Linux on Patreon.
One of the best places to get, and offer, support for Slackware is on the Linux Questions Forum. Another is the Slackware Documentation Project. There's a LOT of information about Slackware out there on the Internet. Slackware is, after all, 33 years old and is extremely well supported by the developers with a very active and helpful online community.
You will certainly benefit from reading the Slackware Linux Esssentials book. Follow the link to view it online or you can download it using 'git' if a local copy is required:
It's also possible to recommend content, revisions, or updates for the official Slackware Linux Esssentials book. Visit the website at https://www.slackbook.org to verify the current status of the book and follow the directions to contribute.
