Jenny’s Daily Drivers: Slackware 15

Picking a “daily driver” operating system is a lot like picking a daily driver car: you want something reliable,
comfortable, and unlikely to strand you in a grocery store parking lot with smoke coming out of the hood.
Slackware 15 is… not a Prius. It’s more like a well-maintained classic pickup: no touchscreen, no lane assist,
but it starts every morning, hauls whatever you ask, and quietly judges you for not knowing how a carburetor works.

In other words, running Slackware 15 as a daily driver is an intentional lifestyle choice. It’s not here to
“disrupt” anything. It’s here to be predictable, stable, and unbothered by trends. If you’ve ever missed the feeling
of actually owning your Linux boxlike, really owning it, down to the bootloader and the init scriptswelcome home.
If you’ve never had that feeling… Slackware is about to hand you the keys and remove the training wheels.

Why Slackware 15 Still Matters (Yes, in a World Full of App Stores)

Slackware has a reputation: old-school, minimalist, and stubbornly consistent. That reputation is earned.
Slackware’s philosophy leans hard into “keep it simple,” meaning the system stays understandable even when it’s doing
something complicated. Instead of hiding the wiring, it labels the wires and trusts you not to chew on them.

1) It’s stable in the “boring is beautiful” sense

Slackware 15.0 shipped as a major stable release and continues to receive updates via its patches and security channels.
The point isn’t to be the newest; it’s to be dependable. When Slackware changes something, it tends to do it for reasons
you can read, verify, and reverse if you disagree.

2) It’s refreshingly systemd-free (without being “anti-modern”)

Slackware uses traditional init-style startup scripts. That can sound quaint until you realize how often “quaint”
translates to “debuggable at 2:00 AM.” When a service starts, you can usually find the script that started it, read it
like a human, and fix it without summoning a ritual circle of dependency graphs.

3) It makes you the grown-up in the room (especially with dependencies)

Slackware’s package tools don’t automatically resolve dependencies. Some people call this “dependency hell.”
Slackware users call it “Tuesday.” The upside is control: you install what you mean to install. The tradeoff is you have
to pay attentionlike an adult, with a calendar and everything.

What’s Inside Slackware 15

Slackware 15.0 modernized a lot while keeping its personality intact. Under the hood you get a Linux 5.15 LTS-era base,
plus big updates across desktops, authentication, multimedia, and developer tooling. In practical terms, Slackware 15 is
absolutely capable of being a contemporary Linux workstationjust one that expects you to read the signs instead of
ignoring them until the GPS starts yelling.

Desktop environments that don’t feel like a time machine

Slackware 15 ships with KDE Plasma 5 (including a 5.23.x generation in the 15.0 timeframe) and Xfce 4.16, giving you the
choice between a full-featured modern desktop and a lightweight, fast environment that doesn’t try to become your
therapist. Wayland support is present alongside X11, so you’re not locked into the pastSlackware just refuses to
pretend the past didn’t work.

Modern plumbing: PAM, elogind, and multimedia options

Slackware 15 adopted PAM, switched to elogind for logind-style session management, and added PipeWire as an alternative
in the audio stack (with PulseAudio still very much part of the conversation). It’s a pragmatic blend: compatibility
where it matters, flexibility where it helps, and minimal drama everywhere.

Developer-friendly by default

Slackware historically ships a “complete system” mindset, and 15.0 continues that tradition with a refreshed toolchain
and support for languages like Python 3 and Rust. If you build software, compile kernels, or like to live dangerously
with source tarballs from obscure corners of the internet, Slackware is oddly comforting.

Installing Slackware 15: The Part Where Jenny Smiles and Everyone Else Googles

Slackware’s installer is famously text-based (ncurses-style), but “text-based” doesn’t mean “hard.” It means “menu-driven,
explicit, and not pretending it can read your mind.” You’ll do partitioning, select packages, set up networking, and pick
a bootloader in a way that feels hands-onbecause it is.

The bootloader cameo: LILO is not dead, it’s just vibing

Depending on your setup, you might encounter LILO as the classic default. And yes, seeing it in 2026 feels a bit like
spotting a payphone that still works. Slackware can be configured with other boot options too, but the broader point is:
Slackware isn’t ashamed of the tools that got the job done for decades.

First boot reality check

Expect a console login first. Graphical login is available, but Slackware won’t assume that’s what you want.
You can start X manually, configure your preferred default, and build the experience you actually intend to use.
This is a feature, not a punishment… although it can feel like both until you’ve had coffee.

Keeping Slackware 15 Updated with slackpkg

If Slackware were a roommate, slackpkg would be the one who posts the chore chart and then calmly watches to see
if you’ll do it. It’s a tool for managing official Slackware packagesupdating, installing, upgrading, and cleaning.
It does not babysit third-party dependencies. That’s your job, and Slackware is very proud of you for having a job.

The basic update flow (a daily-driver habit worth building)

A couple of notes that save real pain:

• Mirror selection matters. slackpkg expects you to uncomment exactly one mirror entry.
• Pay attention to “new config” prompts. Slackware won’t silently overwrite your carefully tweaked files.
• Kernel upgrades are not “set it and forget it.” When the kernel changes, you may need to rebuild your initrd
  and update your bootloader configuration (especially if you’re using LILO or ELILO).

The “daily driver” moment: the kernel upgraded, now what?

This is where Slackware teaches you the kind of Linux knowledge that other distros gently hide behind friendly buttons.
On Slackware, a kernel upgrade may require an initrd rebuild and a bootloader refresh. The system usually gives you the
hint; you supply the follow-through. There’s also a helper script that can generate a sensible mkinitrd command for your
setup, which is basically Slackware’s way of saying, “I believe in you… but I also believe in guardrails.”

Going Beyond the Base System: SlackBuilds, sbopkg, and “Yes, You Read the README”

Slackware’s official repo is solid, but a daily driver needs “normal human stuff” too: extra apps, niche tools, newer
versions, and sometimes weird hobbies like compiling a compiler. That’s where SlackBuilds.org (often called SBo)
comes in: a curated collection of build scripts that create proper Slackware packages from source.

sbopkg: your friendly neighborhood SlackBuilds wrangler

sbopkg syncs a local copy of the SlackBuilds repository, lets you browse packages, and can automate builds via queue
files (especially when combined with the queue generator tooling). In daily-driver terms: it reduces the “manual labor”
without turning Slackware into something it’s not.

The workflow is delightfully consistent: read the README, confirm dependencies, build packages that install cleanly, and
keep your system coherent. It’s slower than “click install,” but it’s also dramatically less mysterious when something
breaks.

slackpkg+ and third-party repositories (useful, but bring caution)

If you want a unified way to manage both official packages and selected third-party repositories, slackpkg+ exists
as a plugin approach. It can help keep binary extras in sync, but it also increases complexity. Daily driver tip:
keep your third-party sources intentional and minimal, and don’t mix repos like you’re making a smoothie.

Daily-Driving the Desktop: KDE Plasma, Xfce, and Actual Work

Here’s the part people don’t always expect: once installed and configured, Slackware 15 can feel quietly modern.
KDE Plasma gives you a polished environment with all the conveniences, while Xfce keeps things light and quick.
The “Slackware difference” is less about what you can do, and more about how much of the system you can understand
while doing it.

Performance: less bloat, more “my computer is still my computer”

Long-time Slackware fans often praise how responsive it feels on older hardware. Some even cite surprisingly low baseline
memory usage and snappy boot behavior compared to heavier setups. Treat that as anecdotal, but the underlying theme is real:
Slackware’s defaults tend to be lean, and it doesn’t add background services just because the cool kids are doing it.

Common daily-driver tasks that Slackware handles well

• Web + email: Modern browsers, mail clients, and the usual productivity stack can be built or installed cleanly.
• Dev work: Compilers, build tools, Python, and Rust support make it friendly for coding and building from source.
• Networking: Once configured, it’s stableespecially for wired setups and predictable desktops.
• Servers-at-heart: Slackware’s calm approach makes it comfortable for people who also run servers.

Practical Example: “I Just Want LibreOffice”

Office suites are the ultimate daily-driver test. You can absolutely get LibreOffice running well on Slackware 15, and the
community has practical guides for installing a current, functional setup. The bigger lesson: Slackware assumes you did a
reasonably complete base install (a common recommendation) and that you’re comfortable doing a few steps in a terminal.
That sounds scary until you realize it’s usually deterministic and repeatable.

Troubleshooting Without Losing Your Mind

Slackware troubleshooting feels different from troubleshooting on a “magic” distro. On Slackware, you don’t hunt for the
hidden settings panel. You look for the file, the script, or the logbecause it’s probably right where it says it is.

Three places you’ll become best friends with

• /etc/rc.d/ classic startup scripts and service toggles (often just executable permissions).
• /var/log/ logs, plus package install records that make auditing changes straightforward.
• /etc/slackpkg/ configuration, mirrors, blacklist patterns, and the knobs you actually control.

Who Should Use Slackware 15 as a Daily Driver

Slackware 15 is a great daily driver if you want:

• Stability over novelty
• Transparency over automation
• A Linux distribution that teaches you how Linux works
• A system you can keep consistent for years

It’s a rough fit if you want:

• Hands-free dependency resolution for everything
• A GUI “app store” experience as your primary workflow
• Constant feature churn (or constant dopamine)

Final Thoughts: Slackware 15 Is a Daily Driver for People Who Like the Driver’s Seat

Slackware 15 doesn’t try to impress you with flashy wizards. It impresses you with how little it surprises you once you
set it up properly. It’s opinionated in the most refreshing way: “Here’s a sane base system. Make it yours.”
If your idea of fun includes understanding your boot process, knowing exactly what started at startup, and installing
software in a way you can audit later, Slackware 15 isn’t just viableit’s delightful.

And if you’re Jenny, you’ll probably enjoy the quiet satisfaction of a system that makes you do a tiny bit of work up front,
then pays you back with months of calm. The kind of calm you only notice after you stop hearing your computer constantly
asking for permission to update its feelings.

Jenny’s 7-Day Daily-Driver Diary (Extra )

Day 1 (Monday): I boot the installer and immediately feel like I’ve walked into a retro diner where the coffee is strong
and the menus don’t have pictures. The ncurses screens are blunt, practical, and weirdly comforting. Partitioning takes a few
minutes of actual thoughtlike, the kind you can’t outsource to a “recommended layout” button. When the bootloader step shows up,
I grin because it’s the kind of moment that reminds you Linux used to be a hobby and a tool. I finish the install, reboot,
and land at a console login. No fireworks. Just a prompt. I respect that.

Day 2 (Tuesday): Time to make it livable. I create a user, sort out groups, and set up networking. Slackware is polite:
it doesn’t assume I want a thousand services, but it also doesn’t block me from enabling what I need. I start X, try both desktops,
and decide my mood today is “Xfce: fast, quiet, and not trying to sell me a cloud subscription.” I spend the evening adjusting config
files like it’s a craft project, because it kind of is.

Day 3 (Wednesday): Updates. I configure a mirror, run the usual slackpkg sequence, and watch it calmly list what’s changing.
No dependency drama. No surprise “let’s remove half your desktop.” Then the kernel update message arrivesthe Slackware equivalent of a sticky note
that says, “Hey, you’re an adult, right?” I rebuild the initrd, update the bootloader bits, and reboot successfully. It’s oddly satisfying:
not because it was hard, but because I know exactly what changed and why.

Day 4 (Thursday): Real work day. Browser, email, SSH, writing, and a bit of coding. The system feels crisp. I notice how little
background noise there isfewer pop-ups, fewer “helper” processes, fewer mysteries. It’s not minimalist in the “nothing works” way; it’s minimalist
in the “everything works because it’s not fighting itself” way. I compile a small tool from source just because I can, and it installs cleanly as a package.
That’s a tiny joy you don’t always get on distros that hide the machinery.

Day 5 (Friday): I want extra software that isn’t in the base set. That’s my cue to visit SlackBuilds territory.
I sync with sbopkg, generate a queue, and let it build in the background while I do other things. The process is slower than a binary repo,
but it’s also surprisingly transparent. The build logs aren’t cryptic; they’re just… honest. By evening, I’ve installed what I need, and my package
database still looks tidy.

Day 6 (Saturday): I switch to KDE Plasma for a “nice things” daymultiple monitors, polished settings, and a desktop that feels modern
without feeling like a social network. I try a Wayland session out of curiosity, then fall back to X11 for the stuff I know is rock-solid.
Slackware doesn’t guilt-trip me either way. It just lets me choose.

Day 7 (Sunday): The real test of a daily driver is whether you forget it exists. Today, I mostly do. The machine boots, connects, works,
and stays out of my way. Slackware 15 isn’t trying to be my assistant. It’s trying to be my system. And honestly? That’s the best kind of relationship.