Slackware Guide

Overview

Slackware was created by Patrick Volkerding in 1993, making it one of the earliest Linux distributions. It remains true to its Unix roots, prioritizing simplicity and stability over convenience features.

Quick Facts

Based On	Independent
Package Manager	pkgtool / slackpkg
Default Desktop	KDE Plasma (multiple available)
Release Cycle	When ready (no fixed schedule)
Support Period	Until next release
Init System	BSD-style init scripts

Warning

Slackware is for experienced Linux users who want full control. It doesn't hold your hand - you're expected to understand what you're doing.

Who Should Use Slackware?

Unix purists - Traditional Unix-like experience
Advanced users - Full control over the system
Stability seekers - Extremely stable packages
Learners - Understand Linux at a deeper level
Minimalists - No unnecessary abstractions

Installation

Slackware uses a text-based installer that's straightforward but traditional:

Download from slackware.com
Boot from the installation media
Login as root (no password)
Partition disk with fdisk or cfdisk
Run setup to start the installer
Select packages and complete installation

bash

# At the boot prompt, login as root
root

# Partition your disk
cfdisk /dev/sda

# Start the installer
setup

# Follow the menu-driven installation:
# - ADDSWAP: Setup swap partition
# - TARGET: Select target partition
# - SOURCE: Select installation source
# - SELECT: Choose package sets
# - INSTALL: Install packages
# - CONFIGURE: Post-installation setup

Package Management

Slackware uses simple tarball-based packages:

bash

# Install a package
installpkg package.txz

# Remove a package
removepkg package-name

# Upgrade a package
upgradepkg package.txz

# Update from mirrors using slackpkg
slackpkg update
slackpkg upgrade-all

# Install new packages
slackpkg install package-name

# Search for packages
slackpkg search keyword

# Third-party packages with sbopkg (SlackBuilds.org)
sbopkg -i package-name

Info

Slackware packages don't track dependencies automatically. You manage dependencies manually, giving you full control but requiring more knowledge.

Key Features

Stability

Slackware releases when ready, not on a schedule. Each release is thoroughly tested for stability.

BSD-style Init

Uses traditional BSD-style init scripts instead of systemd. Clean, understandable system initialization.

Vanilla Packages

Packages are kept as close to upstream as possible. No distribution-specific patches that could introduce bugs or confusion.

SlackBuilds.org

Community repository with build scripts for thousands of additional packages.

Slackware Philosophy

Core Principles

KISS	Keep It Simple, Stupid - no unnecessary complexity
Stability	Prefer stable, tested software over bleeding edge
Unix-like	Follow traditional Unix conventions
User control	Administrator makes decisions, not the distro
Minimal patching	Keep packages close to upstream

FAQ

Why doesn't Slackware have dependency resolution?

By design. Patrick Volkerding believes users should understand what they're installing. Use sbopkg or slapt-get if you want dependency tracking.

Is Slackware still actively maintained?

Yes! Slackware 15.0 was released in 2022 after years of development. The -current branch receives regular updates.

How do I get additional software?

SlackBuilds.org has thousands of build scripts. Install sbopkg to easily build and install from this repository.

Summary

Slackware offers a pure, Unix-like Linux experience for those who value simplicity and control. Key takeaways:

Oldest actively maintained Linux distribution
KISS philosophy with minimal abstraction
BSD-style init instead of systemd
Manual dependency management
Extremely stable and reliable