Linux on Danilo Falcão da Silva

The Shell That Finally Got Out of My Way

Wed, 27 May 2026 01:07:05 -0300

I use Zsh with Oh My Zsh.

That one line summarizes a big shift in how I work every day. I did not switch because Bash is bad. I love Bash and respect it. Bash is stable, everywhere, script-friendly, and still the safest common denominator when I touch unknown Linux boxes.

I switched because my daily workflow changed, and Bash stopped fitting that workflow.

The Bash pain point that finally made me move

The biggest Bash pain point for me was history behavior across multiple terminals.

Btrfs vs ZFS on Linux in 2026: Practical Winner, Technical Winner

Mon, 25 May 2026 19:56:00 -0300

Btrfs is king on Linux. Not because it’s technically superior to ZFS in every dimension — it isn’t — but because it ships in the kernel, installs without friction, and integrates with every major distro’s tooling out of the box. In 2026, if you format a fresh Fedora, openSUSE, or Ubuntu Desktop installation, you’re running Btrfs by default. ZFS requires you to want it badly enough to fight the packaging.

tmux vs GNU Screen — why I moved on after twenty years

Sun, 24 May 2026 22:00:00 -0300

I ran GNU Screen for more than twenty years. It was one of the first tools I installed on every machine, right after vim and ssh. Screen kept long compilations alive through flaky connections, let me juggle IRC and tail logs on the same VT100, and never once lost a session I cared about. For a tool born in 1987, that is a remarkable track record.

About fifteen years ago I switched to tmux. It was not because Screen broke. It was because tmux made me faster at work I was already doing, and then it kept getting better while Screen stood still. I have not looked back.

AI Bug Reports: The Real Vulnerability Is That We Weren't Looking Hard Enough

Sat, 23 May 2026 10:00:00 -0300

On May 18, 2026, Linus Torvalds called the Linux kernel security mailing list “almost entirely unmanageable.” The reason: a flood of AI-generated bug reports. The reaction was predictable — ban AI, blame researchers, declare the tools aren’t ready.

I wrote about the maintenance crisis last week and I think that framing misses the deeper story. The problem is not that AI is generating too many reports. The problem is that the code was more broken than we thought, and for twenty years nobody had the tools to look at it properly.

Ansible, Puppet, Chef and SaltStack: Why Ansible Is Still My Default in 2026

Fri, 22 May 2026 09:00:00 -0300

There are four names that come up when you ask how to manage configuration at scale. I’ve used all four, in production, over the last fifteen years. The answer to “which one” is not the one that wins benchmarks — it’s the one that matches how your team thinks about change.

The shortlist hasn’t changed since the early 2010s: Ansible, Puppet, Chef, SaltStack. The ownership has changed. The licences have changed. The community gravity has very much changed. Ansible sits at 31.94% market share for new projects as of early 2026 and is, by a wide margin, the most-adopted tool for new configuration-management work. Puppet holds 12.41%, Chef around 6.70%, and Salt has fallen out of the top-tier mindshare entirely even though the codebase is still actively developed under Broadcom.

Notion vs Obsidian: Local-First Sounds Great Until You Have to Sync It

Thu, 21 May 2026 07:00:00 -0300

I configure infrastructure for a living. Containers, reverse proxies, NFS mounts, certificate renewals, sync layers between machines — that’s most days. The last thing I want when I open my personal note-taking app is another sync layer to babysit. That, more than anything else, is why I picked Notion over Obsidian.

This is the honest read on Notion vs Obsidian for one person, one phone, one Linux desktop, and the occasional browser tab on someone else’s machine. The headline: Obsidian is the purer architecture and the wrong fit for me. Notion is the lazy architecture that does the right thing without asking. For a personal knowledge base, lazy wins.

Age Verification Laws Are Coming for Your OS. Linux Doesn't Care.

Wed, 20 May 2026 21:40:00 -0300

For most of 2025 the age-verification conversation was about porn sites. By the end of the year it had moved up the stack. By 2026 it is at the operating system, and that is where the story gets interesting for anyone who cares about how Linux is built.

Nine US states put age-verification laws in force during 2025 alone: South Carolina (Jan 1), Florida (Jan 1), Tennessee (Jan 13), Georgia (Jul 1), Wyoming (Jul 1), North Dakota (Aug 1), Arizona (Sep 26), Ohio (Sep 30), and Missouri (Nov 30). Roughly half the country now mandates some form of age gate for adult content, social media, or both.

Hermes Agent vs OpenClaw: Why I Run Hermes Every Day

Wed, 20 May 2026 14:30:00 -0300

There are two open-source autonomous agents in 2026 worth a serious DevOps engineer’s time, and they have made opposite architectural bets. I tried both. I run Hermes Agent every day. This is the analysis of why — not a both-sides post, not a head-to-head benchmark, but a direct argument that one of these two architectures is right for infrastructure work and the other one isn’t.

The headline: agent-first beats gateway-first when the work rewards familiarity. Most infrastructure work does. The rest of this post is the why.

AI Bug Reports Are Drowning Open Source — And the Fix Isn't 'Stop Using AI'

Wed, 20 May 2026 10:00:00 -0300

On May 18, 2026, Linus Torvalds said the Linux kernel security mailing list had become “almost entirely unmanageable” because of duplicate AI-generated bug reports. Two months earlier, longtime stable maintainer Willy Tarreau had already shared the numbers: a list that received two to three reports per week in 2024 was getting five to ten reports per day by March 2026. In January, Daniel Stenberg shut down the curl bug bounty after the valid-report rate on HackerOne dropped from above 15% to below 5%, with twenty submissions in 21 days — seven of them in one 16-hour window — and zero real vulnerabilities among them.

KDE Plasma 6.7 Is Coming June 16th — And I Cannot Wait

Wed, 20 May 2026 09:30:00 -0300

KDE shipped the Plasma 6.7 Beta on May 14, 2026. The final release lands on June 16. I’m still on Plasma 6.6.5 — the stable that shipped in Fedora 44 — and I’m going to stay there until 6.7 hits Fedora’s repos. But I have been reading every announcement, every “This Week in Plasma” post, and every release-note dump KDE has been putting out, and I want to say this clearly:

NVIDIA on Fedora KDE Wayland in 2026: Field Report from an RTX 5070

Tue, 19 May 2026 14:00:00 -0300

NVIDIA on Linux has been a punchline for so long that “just buy AMD” was the standard advice in every Linux subreddit thread. In 2026, on Fedora 44 with KDE Plasma 6.6 on Wayland, running an RTX 5070 (Blackwell) with the 595 driver branch, I want to say something different:

It’s fine. It’s actually fine.

Not “fine if you don’t use Wayland.” Not “fine if you stick to X11.” Fine, full stop. This is the short, honest report of how I run it.

Why I Left Ubuntu Desktop — and Picked Debian Over Ubuntu Server

Tue, 19 May 2026 12:00:00 -0300

I ran Ubuntu on my workstation from Hardy Heron in 2008 to about Jammy in 2022. Fifteen years. It was the first Linux I trusted on servers I cared about, the first one that made hardware support feel solved, and for a long stretch it was the obvious answer to “what Linux should a sane person install?”

I don’t run it on my desktop anymore. I don’t run Ubuntu Server either — though that’s a personal-taste call and not a knock on the product, which is still a perfectly good distribution that I’d happily recommend to most people. Ubuntu has split in half: the server side is still strong, the desktop side has gone somewhere I’m not willing to follow, and the two halves deserve very different treatment. Especially because we just got Ubuntu 26.04 LTS “Resolute Raccoon” on April 23, and the headlines are mostly cheerful about features that don’t fix the things that actually drove me away.

NetBird: The Self-Hosted Mesh VPN I Wanted Tailscale to Be

Tue, 19 May 2026 11:30:00 -0300

I have been carrying a quiet grudge about Tailscale for two years. The product is excellent. The clients are polished. The “log in with Google and you have a mesh in 60 seconds” experience is genuinely magical. But the control plane — the part that decides which of your machines can talk to which other machines, and where the keys for that decision live — is closed source and hosted exclusively by Tailscale. You can run Headscale to reimplement it open-source, but you’re still bringing along Tailscale’s proprietary clients on most platforms.

Claude Code, opencode, Cursor: My Daily Driver and My Plan B

Tue, 19 May 2026 11:00:00 -0300

I’ve spent enough of the last six months working alongside an AI coding agent that I now have actual opinions, in the way you only get from shipping production code with a tool, not from reading benchmarks about it. There are three names that dominate the conversation in 2026 and they represent three genuinely different bets about how humans and language models should collaborate on code.

This is my honest read on Cursor, Claude Code, and opencode. The headline: Claude Code is my daily driver. opencode is my Plan B. Cursor is not what I reach for. Here’s why.

Distrobox, Toolbx, and the 'What Would You Give and What Would You Keep' Question

Tue, 19 May 2026 10:30:00 -0300

“What would you give and what would you keep?” — Mase, From Scratch (Double Up, 1999)

Mase asked it about rewinding your whole life and starting over. I ask it every time someone on my team picks a development container stack. Because the moment you decide to let a container be your workstation — not just hold a service, but hold your editor, your shell, your language toolchains, your AUR packages on top of a Fedora host — you’re making a series of small, ugly trade-offs. What would you give up from your bare-metal workflow, and what would you keep?

Steam Machine 2026: Round Two, and This Time It Runs KDE

Tue, 19 May 2026 09:00:00 -0300

The first Steam Machine was a 2015 disaster. A confused, fragmented launch of third-party boxes running an immature SteamOS 1, no AAA Linux catalogue, no Proton, and a controller everyone politely pretended to like. The whole effort quietly evaporated within a couple of years and Valve, to its credit, didn’t try to spin it. They went away, built the Steam Deck, built Proton into something that actually works, and waited.

Zed 1.0: When 'Fast Editor' Finally Stops Being a Marketing Line

Mon, 18 May 2026 21:00:00 -0300

I have a complicated relationship with code editors. I used vim for fifteen years out of stubbornness, switched to VS Code because the ecosystem made it impossible not to, and have spent the last four years quietly resenting it every time the laptop fans spin up because I opened three monorepos and a markdown file.

Zed 1.0 shipped at the end of April 2026. I’ve been running it as my daily driver for the two weeks since, and I’m writing this post in it. Here’s where I’ve actually landed, including the things I think the typical Zed review under-sells.

Fedora 44: A KDE-Heavy, DevOps-Tinted First Look

Mon, 18 May 2026 15:30:00 -0300

Fedora Linux 44 shipped on April 28, 2026, two weeks behind its original date after a late-cycle batch of blockers. I’ve been running it on my KDE daily-driver for a couple of weeks now. It’s the kind of release that doesn’t scream — no single tentpole feature — but if you spend your day on Linux, the cumulative effect is real. Here’s what stood out to me, with a bias toward what I actually noticed.