
The perfect Plasma that was useless
Arch Linux installation complete. Plasma was beautiful, gleaming, with Wayland running like a magazine ad. It was just missing a terminal. And the file manager. And anything useful at all.

Arch Linux installation complete. Plasma was beautiful, gleaming, with Wayland running like a magazine ad. It was just missing a terminal. And the file manager. And anything useful at all.

Logbook, Stardate 1337.15 Today is Slackware day, Stubborn ones! Time to install the grandfather of them all, again, for the thousandth time. Though it’s only the fourth or fifth installation of it in 2026. Hopefully the last one. Before you ask: why on earth install Slackware Linux in 2026? It’s Jurassic, has no automatic dependency resolution, is a pain to maintain over time, and its current release — 15.0 — is already showing its age, getting a bit too stale for comfort. And I ask back: why not? It’ll be instructive at the very least, even fun. For a nerd, anyway. ...

Surviving the first contact with Arch Linux A slight exaggeration on my part — I’ve had contact with Arch Linux before. Long before systemd, back when it used a logical and rational init system. Sometime last century, perhaps? I’d been away from it for a long time. But that’s beside the point. The point is, I need to be honest right from the start: I shouldn’t be writing this post. ...

Before the first boot, there was only the void… Or rather: there was an FX-6300 with 8 GB of RAM, an Nvidia GeForce GT-610 graphics card that can barely render a desktop, a 1 TB HDD eager to host AI models, and the stubbornness of someone who could never quite quit Linux for good. Old but running Linux. Suck on that, Windows 11. My name is Marcelo Souza (or just “The Stubborn One”), I’m a Designer by trade, an old-school nerd/geek, and this is teimosodolinux.github.io — a technical and existential logbook of my adventures (and misadventures) with Linux in 2026. ...

In the previous post, I talked a big game, bragged about how I had managed to get the blog up and running almost perfectly. Bullshit. It was a beating. I was almost defeated by a stray slash in a markdown file. At least now I have at least one functional comment field — I think. It still needs testing in production. The first cold shower was pushing the blog live after the official commit and seeing that exasperating 404 error message. “Oh come on, now what? This never happened on Blogger…” ...

I had a simple goal: start a blog to share my technical adventures and misadventures involving Linux, free software and related subjects. I came up with a solid structure, an honest layout, did some research on platforms and that was it — I decided to host everything on GitHub. It seemed like a logical and natural path, since a blog about Open Source has to live on GitHub, right? Seemed right. ...