<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Larvitz Blog</title><link>https://hofstede.it/</link><description>FreeBSD, Linux, all things cleanly engineered</description><atom:link href="https://hofstede.it/feeds/all.rss.xml" rel="self"/><lastBuildDate>Tue, 17 Nov 2026 00:00:00 +0100</lastBuildDate><item><title>One Old JavaCard, Two Lives: Kerberos PKINIT and SSH From a Drawer Find</title><link>https://hofstede.it/one-old-javacard-two-lives-kerberos-pkinit-and-ssh-from-a-drawer-find/</link><description>&lt;p&gt;An old &lt;span class="caps"&gt;NXP&lt;/span&gt; JavaCard was about to become e-waste. Instead it got an applet loaded with GlobalPlatformPro, became a &lt;span class="caps"&gt;PKCS&lt;/span&gt;#15 token, received a certificate from my IdM &lt;span class="caps"&gt;CA&lt;/span&gt; and fetched a Kerberos ticket via &lt;span class="caps"&gt;PKINIT&lt;/span&gt;. Ninety minutes later the same card was wiped, turned into an OpenPGP card and logged in to a FreeBSD server over &lt;span class="caps"&gt;SSH&lt;/span&gt;. This is how both lives worked, and the six places where they did not work on the first&amp;nbsp;try.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Tue, 17 Nov 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-11-17:/one-old-javacard-two-lives-kerberos-pkinit-and-ssh-from-a-drawer-find/</guid><category>Linux</category><category>javacard</category><category>smartcard</category><category>globalplatform</category><category>opensc</category><category>pkcs15</category><category>freeipa</category><category>idm</category><category>kerberos</category><category>pkinit</category><category>openpgp</category><category>ssh</category><category>fedora</category><category>security</category></item><item><title>Git Beyond the Basics: Worktrees, Cherry-Picks and Signed Commits</title><link>https://hofstede.it/git-beyond-the-basics-worktrees-cherry-picks-and-signed-commits/</link><description>&lt;p&gt;Almost every Git tutorial stops after add, commit, push and a merge conflict. The tools that make Git pleasant in daily work get far less attention: worktrees for parallel feature branches, cherry-picks for backports, fixup commits and autosquash for clean history, the reflog for recovering from mistakes, and signed commits that prove who made them. This article starts with the mental model and the basics, then works through the parts I actually use, including signing with an OpenPGP smartcard through&amp;nbsp;oct-git.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Mon, 16 Nov 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-11-16:/git-beyond-the-basics-worktrees-cherry-picks-and-signed-commits/</guid><category>Linux</category><category>git</category><category>version-control</category><category>lazygit</category><category>worktree</category><category>cherry-pick</category><category>rebase</category><category>signing</category><category>openpgp</category><category>smartcard</category><category>oct-git</category><category>ssh</category><category>forgejo</category><category>fedora</category><category>freebsd</category></item><item><title>An IdM Replica at Home: Kerberos That Survives a Dead Tunnel</title><link>https://hofstede.it/an-idm-replica-at-home-kerberos-that-survives-a-dead-tunnel/</link><description>&lt;p&gt;My two Red Hat Identity Management servers live in a data center, and every &lt;span class="caps"&gt;SSH&lt;/span&gt; login at home depends on a WireGuard tunnel to reach them. This is how a third replica ended up in a bhyve &lt;span class="caps"&gt;VM&lt;/span&gt; on my home hypervisor: a &lt;span class="caps"&gt;DMZ&lt;/span&gt; that only exists inside the host, a tunnel that only worked in one direction, location-aware &lt;span class="caps"&gt;DNS&lt;/span&gt; that was less location-aware than I thought, and a test with the tunnel switched&amp;nbsp;off.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sat, 14 Nov 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-11-14:/an-idm-replica-at-home-kerberos-that-survives-a-dead-tunnel/</guid><category>Linux</category><category>freeipa</category><category>idm</category><category>kerberos</category><category>rhel</category><category>bhyve</category><category>freebsd</category><category>opnsense</category><category>wireguard</category><category>ipv6</category><category>dns</category><category>homelab</category></item><item><title>A Read-Only AI Reviewer for Forgejo Pull Requests</title><link>https://hofstede.it/a-read-only-ai-reviewer-for-forgejo-pull-requests/</link><description>&lt;p&gt;A small Python service that reviews every pull request on my self-hosted Forgejo with an &lt;span class="caps"&gt;LLM&lt;/span&gt;, posts a summary and inline findings, and is not allowed to do anything else. The interesting part was not getting a model to comment on a diff. It was getting it to stop being confidently wrong about code it had never seen, and making sure a misbehaving or manipulated bot could not change a single&amp;nbsp;line.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 08 Nov 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-11-08:/a-read-only-ai-reviewer-for-forgejo-pull-requests/</guid><category>Linux</category><category>forgejo</category><category>ai</category><category>llm</category><category>code-review</category><category>podman</category><category>quadlets</category><category>python</category><category>self-hosting</category><category>security</category><category>openrouter</category></item><item><title>Hardware Keys Without GnuPG: The Rust OpenPGP Card Stack, Now in FreeBSD Ports</title><link>https://hofstede.it/hardware-keys-without-gnupg-the-rust-openpgp-card-stack-now-in-freebsd-ports/</link><description>&lt;p&gt;Three small Rust tools from the OpenPGP Card project replace the GnuPG stack for my everyday hardware key work: oct to manage OpenPGP cards and Nitrokeys, oct-git to sign Git commits, and openpgp-card-ssh-agent as a hardware-backed &lt;span class="caps"&gt;SSH&lt;/span&gt; agent. I ported all three to FreeBSD and they are now in the ports tree. This article explains what each tool does, how they share &lt;span class="caps"&gt;PIN&lt;/span&gt; handling, and how I set them up on Fedora and on my FreeBSD&amp;nbsp;T480.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Thu, 05 Nov 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-11-05:/hardware-keys-without-gnupg-the-rust-openpgp-card-stack-now-in-freebsd-ports/</guid><category>FreeBSD</category><category>freebsd</category><category>linux</category><category>fedora</category><category>openpgp</category><category>smartcard</category><category>nitrokey</category><category>ssh</category><category>git</category><category>rust</category><category>ports</category><category>pkg</category><category>security</category></item><item><title>Linux Foundationals: From Silicon to Userspace - The Boot and Init Chain</title><link>https://hofstede.it/linux-foundationals-from-silicon-to-userspace-the-boot-and-init-chain/</link><description>&lt;p&gt;The first article in the Linux Foundationals series. It traces a Fedora system from the &lt;span class="caps"&gt;UEFI&lt;/span&gt; handoff through shim and Secure Boot, &lt;span class="caps"&gt;MOK&lt;/span&gt; enrollment with mokutil, &lt;span class="caps"&gt;GRUB2&lt;/span&gt; and Boot Loader Specification entries, the dracut initramfs and switch_root, all the way to systemd as &lt;span class="caps"&gt;PID&lt;/span&gt; 1. Then it covers units, dependencies versus ordering, targets, and how to measure and fix a slow boot with&amp;nbsp;systemd-analyze.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sat, 31 Oct 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-10-31:/linux-foundationals-from-silicon-to-userspace-the-boot-and-init-chain/</guid><category>Linux</category><category>linux</category><category>linux-foundationals</category><category>fedora</category><category>rhel</category><category>boot</category><category>uefi</category><category>secure-boot</category><category>shim</category><category>mokutil</category><category>grub</category><category>dracut</category><category>initramfs</category><category>systemd</category><category>systemd-analyze</category></item><item><title>php2shell on arm64: Building Fixed PHP Packages Without Poudriere</title><link>https://hofstede.it/php2shell-on-arm64-building-fixed-php-packages-without-poudriere/</link><description>&lt;p&gt;The php2shell fix landed in the FreeBSD ports tree within a day, but packages had only been built for some &lt;span class="caps"&gt;CPU&lt;/span&gt; architectures, and my arm64 jail host was not among them. Instead of setting up Poudriere for a one-off job, I built the fixed &lt;span class="caps"&gt;PHP&lt;/span&gt; 8.5.12 in a throwaway Bastille jail, turned the result into a tiny local pkg repository and upgraded the affected jails from&amp;nbsp;it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Thu, 22 Oct 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-10-22:/php2shell-on-arm64-building-fixed-php-packages-without-poudriere/</guid><category>FreeBSD</category><category>freebsd</category><category>php</category><category>php2shell</category><category>security</category><category>ports</category><category>pkg</category><category>bastille</category><category>jails</category><category>arm64</category><category>aarch64</category></item><item><title>WinBoat Broke, Windows Kept Running: dockurr/windows with Plain Podman</title><link>https://hofstede.it/winboat-broke-windows-kept-running-dockurrwindows-with-plain-podman/</link><description>&lt;p&gt;After a cleanup broke my WinBoat installation, I brought the same Windows 11 &lt;span class="caps"&gt;VM&lt;/span&gt; back with a single rootless podman run against the old storage directory. Here is what dockurr/windows actually is, what lives in its storage folder, why &lt;span class="caps"&gt;NETWORK&lt;/span&gt;=nat quietly became passt in rootless Podman, how I verified &lt;span class="caps"&gt;RDP&lt;/span&gt; without opening a window, and a Quadlet unit to keep it&amp;nbsp;around.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Fri, 16 Oct 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-10-16:/winboat-broke-windows-kept-running-dockurrwindows-with-plain-podman/</guid><category>Linux</category><category>podman</category><category>windows</category><category>qemu</category><category>kvm</category><category>dockurr</category><category>winboat</category><category>rdp</category><category>quadlet</category><category>rootless</category><category>fedora</category></item><item><title>The T480 Is Back: My FreeBSD 15.1 Laptop, From Boot to Browser</title><link>https://hofstede.it/the-t480-is-back-my-freebsd-151-laptop-from-boot-to-browser/</link><description>&lt;p&gt;My ThinkPad T480 now runs FreeBSD 15.1 as a complete desktop: Xfce 4.20, 5 GHz Wi-Fi, verified &lt;span class="caps"&gt;VA&lt;/span&gt;-&lt;span class="caps"&gt;API&lt;/span&gt; video decoding in Firefox and Chromium, Bluetooth audio, a webcam that handles Zoom calls in Firefox, a smart-card-backed &lt;span class="caps"&gt;SSH&lt;/span&gt; and Git workflow, and coding agents. Here are the packages, configuration, tests and machine-specific traps behind a laptop I can simply&amp;nbsp;use.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Thu, 15 Oct 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-10-15:/the-t480-is-back-my-freebsd-151-laptop-from-boot-to-browser/</guid><category>FreeBSD</category><category>freebsd</category><category>thinkpad</category><category>t480</category><category>xfce</category><category>wifi</category><category>vaapi</category><category>bluetooth</category><category>power</category><category>zfs</category><category>pf</category><category>chezmoi</category><category>openpgp</category><category>codex</category><category>crush</category></item><item><title>ArtCraft: Desktop Apps Built with AI, Useful Results, and Open Questions</title><link>https://hofstede.it/artcraft-rust-agent-desktop-apps/</link><description>&lt;p&gt;ArtCraft is attempting to rebuild familiar creative and office applications in Rust with &lt;span class="caps"&gt;AI&lt;/span&gt; coding agents. PhotoCraft worked for my thumbnails, the applications started quickly, and native FreeBSD builds exist. Those are interesting observations, but they do not establish equivalence with Photoshop or Office. A look at the project, its agent-friendly architecture, and the questions that remain about correctness, maintenance and its&amp;nbsp;future.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Tue, 13 Oct 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-10-13:/artcraft-rust-agent-desktop-apps/</guid><category>Open Source</category><category>artcraft</category><category>rust</category><category>ai</category><category>agents</category><category>freebsd</category><category>linux</category><category>desktop</category><category>open-source</category><category>photocraft</category><category>wordcraft</category><category>automation</category></item><item><title>The Ansible Guy Finally Automates His Own Patching: FreeBSD, Jails, Proxmox and RHEL</title><link>https://hofstede.it/the-ansible-guy-finally-automates-his-own-patching-freebsd-jails-proxmox-and-rhel/</link><description>&lt;p&gt;I write Ansible for a living, and I still patched most of my own servers by hand every week. This is how that ended: a Git-based inventory, defensive patch playbooks for FreeBSD (freebsd-update and pkgbase), Bastille thin jails, classic thick jails via my jailexec connection plugin, a Proxmox cluster and &lt;span class="caps"&gt;RHEL&lt;/span&gt;. Ansible Automation Platform runs it for me, but nothing here requires it. Plus the mistakes, including the reboot policy I should have checked before the first real&amp;nbsp;run.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 11 Oct 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-10-11:/the-ansible-guy-finally-automates-his-own-patching-freebsd-jails-proxmox-and-rhel/</guid><category>FreeBSD</category><category>ansible</category><category>freebsd</category><category>jails</category><category>bastille</category><category>pkgbase</category><category>proxmox</category><category>debian</category><category>rhel</category><category>patching</category><category>automation</category><category>aap</category><category>jailexec</category></item><item><title>Claude Code on a FreeBSD Desktop: Plasma, xrdp, the Linuxulator and One Very Confusing PATH</title><link>https://hofstede.it/claude-code-on-a-freebsd-desktop-plasma-xrdp-the-linuxulator-and-one-very-confusing-path/</link><description>&lt;p&gt;A FreeBSD 15.1 Plasma desktop in a Proxmox &lt;span class="caps"&gt;VM&lt;/span&gt;, reachable over xrdp, running Claude Code as a Linux binary through the Linuxulator. Along the way: an Xorg that found no screens, a &lt;span class="caps"&gt;KRDP&lt;/span&gt; package that does not exist, a VirtIO-&lt;span class="caps"&gt;GPU&lt;/span&gt; that gives you a framebuffer but no acceleration, and a &amp;#8220;version regression&amp;#8221; that turned out to be two Claude installations fighting over my &lt;span class="caps"&gt;PATH&lt;/span&gt;. Then I let the agent firewall the machine it was running on, and it did that more carefully than I usually do. It also got one thing wrong, and of course it was the thing about&amp;nbsp;root.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Wed, 07 Oct 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-10-07:/claude-code-on-a-freebsd-desktop-plasma-xrdp-the-linuxulator-and-one-very-confusing-path/</guid><category>FreeBSD</category><category>freebsd</category><category>linuxulator</category><category>claude-code</category><category>ai</category><category>agents</category><category>kde</category><category>plasma</category><category>xrdp</category><category>proxmox</category><category>virtio-gpu</category><category>pf</category><category>doas</category></item><item><title>FreeBSD Foundationals: rc.d - The Service Framework That Fits in Your Head</title><link>https://hofstede.it/freebsd-foundationals-rcd-the-service-framework-that-fits-in-your-head/</link><description>&lt;p&gt;The fourth in the FreeBSD Foundationals series. This one picks up where the boot article stopped, at the moment init runs /etc/rc. It covers how rc finds and orders scripts with rcorder, how rc.conf and its layers are really just shell, what rc.subr gives you for free, how to drive it all with service and sysrc (including inside jails), how to write a correct rc.d script for your own daemon using daemon(8) supervision, and the pidfile trap that makes &amp;#8220;service stop&amp;#8221; restart your process instead of stopping it. Then an honest audit of the rc.d scripts running my own Mastodon, Zigbee2MQTT and NetBox jails. Plus service jails, debugging, and an honest comparison with systemd&amp;nbsp;units.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 04 Oct 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-10-04:/freebsd-foundationals-rcd-the-service-framework-that-fits-in-your-head/</guid><category>FreeBSD</category><category>freebsd</category><category>rc.d</category><category>rc.subr</category><category>rcorder</category><category>rc.conf</category><category>sysrc</category><category>service</category><category>daemon</category><category>init</category><category>service-jails</category><category>jails</category></item><item><title>Self-Hosted AI: Qwen 3.8 on a Rented Blackwell at 150 Tokens per Second</title><link>https://hofstede.it/self-hosted-ai-qwen-38-on-a-rented-blackwell-at-150-tokens-per-second/</link><description>&lt;p&gt;An open-weight Qwen 3.8 27B model, an &lt;span class="caps"&gt;RTX&lt;/span&gt; &lt;span class="caps"&gt;PRO&lt;/span&gt; 6000 Blackwell rented by the hour, and one shell command to start it. For most of my everyday coding it is good enough, it answers at roughly 150 tokens per second, and my prompts stay on infrastructure I chose. Some honest caveats about what &amp;#8220;self-hosted&amp;#8221; means on someone else&amp;#8217;s &lt;span class="caps"&gt;GPU&lt;/span&gt; are included, along with the workflow that has worked best for me: a frontier model for architecture, and a fast open-weight model for the token-heavy implementation&amp;nbsp;loop.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sat, 03 Oct 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-10-03:/self-hosted-ai-qwen-38-on-a-rented-blackwell-at-150-tokens-per-second/</guid><category>Linux</category><category>ai</category><category>llm</category><category>self-hosting</category><category>qwen</category><category>runpod</category><category>sglang</category><category>nvidia</category><category>blackwell</category><category>data-sovereignty</category><category>linux</category></item><item><title>My Ansible Plugin Had a Jail Escape: CVE-2026-55074</title><link>https://hofstede.it/my-ansible-plugin-had-a-jail-escape-cve-2026-55074/</link><description>&lt;p&gt;For almost a year, my jailexec connection plugin let a compromised FreeBSD jail redirect a root-owned write onto the jail host. The input validation was fine. The problem was on which side of the jail boundary the paths were resolved. This is the story of the bug, the fix in 2.0.0, and the &lt;span class="caps"&gt;CVE&lt;/span&gt; that came with&amp;nbsp;it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 27 Sep 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-09-27:/my-ansible-plugin-had-a-jail-escape-cve-2026-55074/</guid><category>FreeBSD</category><category>freebsd</category><category>ansible</category><category>jails</category><category>security</category><category>cve</category><category>symlinks</category><category>disclosure</category></item><item><title>No Proxmox Backup Client for RHEL? Hold My Container Runtime</title><link>https://hofstede.it/pbs-client-rhel-container/</link><description>&lt;p&gt;&lt;span class="caps"&gt;RHEL&lt;/span&gt; 10 on &lt;span class="caps"&gt;ARM64&lt;/span&gt;, a Proxmox Backup Server, and no convenient native client package. I borrowed the client from an old server container, mounted the host root filesystem read-only, and gave SELinux a very specific explanation. Five minutes later, I had an encrypted, incremental backup. There are caveats. Updated 2026-10-18 with a maintained client image for x86_64 and aarch64 on&amp;nbsp;ghcr.io.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Thu, 17 Sep 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-09-17:/pbs-client-rhel-container/</guid><category>Linux</category><category>linux</category><category>rhel</category><category>aarch64</category><category>arm64</category><category>podman</category><category>containers</category><category>proxmox</category><category>backup</category><category>selinux</category></item><item><title>Ansible Automation Platform, Powered by Arch Linux. BTW.</title><link>https://hofstede.it/ansible-execution-environment-arch-btw/</link><description>&lt;p&gt;I built an Arch Linux execution environment, taught pacman to answer to microdnf, and let Ansible Automation Platform use it to patch &lt;span class="caps"&gt;RHEL&lt;/span&gt; systems. The job succeeded. This is evidence, not a&amp;nbsp;recommendation.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sat, 12 Sep 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-09-12:/ansible-execution-environment-arch-btw/</guid><category>Linux</category><category>linux</category><category>rhel</category><category>archlinux</category><category>ansible</category><category>ansible-automation-platform</category><category>podman</category><category>containers</category><category>unsupported</category></item><item><title>Bespoke: A Programming Language for People Who Say Please</title><link>https://hofstede.it/bespoke-a-programming-language-for-people-who-say-please/</link><description>&lt;p&gt;Modern programming languages are full of violence, vulgar abbreviations, and naked imperatives. Bespoke is a statically typed alternative in which exceptions are regrettable circumstances, mutexes grant private audiences, and every request to the compiler ends with a proper&amp;nbsp;thank-you.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sat, 05 Sep 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-09-05:/bespoke-a-programming-language-for-people-who-say-please/</guid><category>Programming</category><category>programming</category><category>language design</category><category>compilers</category><category>concurrency</category><category>humour</category><category>british english</category></item><item><title>Running Citrix Workspace on Fedora with Rootless Podman</title><link>https://hofstede.it/running-citrix-workspace-on-fedora-with-rootless-podman/</link><description>&lt;p&gt;Citrix Workspace is an application I need but do not want woven into my workstation. I put its official Debian package in a disposable rootless Podman container, then pass through just enough X11, PipeWire, &lt;span class="caps"&gt;GPU&lt;/span&gt;, and webcam plumbing to open downloaded &lt;span class="caps"&gt;ICA&lt;/span&gt; files from Fedora&amp;#8217;s file&amp;nbsp;manager.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Thu, 03 Sep 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-09-03:/running-citrix-workspace-on-fedora-with-rootless-podman/</guid><category>Linux</category><category>citrix</category><category>citrix workspace</category><category>ica</category><category>podman</category><category>containers</category><category>fedora</category><category>linux</category><category>rootless</category><category>x11</category></item><item><title>I Wanted an IPv4 Toast and Accidentally Built an IP Service</title><link>https://hofstede.it/i-wanted-an-ipv4-toast-and-accidentally-built-an-ip-service/</link><description>&lt;p&gt;At 10:15 this morning I added a gently condescending toast for IPv4-only visitors to hofstede.it. It called ipify, which felt increasingly inappropriate for somebody operating an &lt;span class="caps"&gt;ASN&lt;/span&gt;. Three hours later I had written a Rust &lt;span class="caps"&gt;IP&lt;/span&gt;-information service, put it behind Caddy, given it three &lt;span class="caps"&gt;DNS&lt;/span&gt; names, and deployed it in its own dual-stack FreeBSD &lt;span class="caps"&gt;VNET&lt;/span&gt; jail. This is how a two-line dependency became&amp;nbsp;infrastructure.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sat, 29 Aug 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-08-29:/i-wanted-an-ipv4-toast-and-accidentally-built-an-ip-service/</guid><category>Networking</category><category>ipv6</category><category>ipv4</category><category>freebsd</category><category>bastille</category><category>jails</category><category>rust</category><category>axum</category><category>caddy</category><category>maxmind</category><category>self-hosting</category></item><item><title>bhyve Inside a Jail: The FreeBSD Feature Nobody Uses</title><link>https://hofstede.it/bhyve-inside-a-jail-the-freebsd-feature-nobody-uses/</link><description>&lt;p&gt;A jail shares the host kernel, so sooner or later you need a real virtual machine. bhyve has been able to run inside a jail since FreeBSD 12.0, and almost nobody does it. This is the full build from my production hypervisor: the devfs ruleset, the four things that have to line up, the two-tier bridge topology, and an honest account of what allow.vmm does and does not buy&amp;nbsp;you.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Thu, 27 Aug 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-08-27:/bhyve-inside-a-jail-the-freebsd-feature-nobody-uses/</guid><category>FreeBSD</category><category>freebsd</category><category>bhyve</category><category>virtualization</category><category>jails</category><category>vm-bhyve</category><category>zfs</category><category>vnet</category><category>networking</category></item><item><title>Crawlfest: Building a Terminal Roguelike in Rust</title><link>https://hofstede.it/crawlfest-building-a-terminal-roguelike-in-rust/</link><description>&lt;p&gt;For a few months now I have been building a terminal roguelike in Rust in the spirit of &lt;span class="caps"&gt;ADOM&lt;/span&gt; and NetHack. This article is about the technical groundwork: why ratatui and legion instead of a game engine, how the four map generators work (rooms, cellular-automata caverns, hand-drawn prefabs, and a hybrid of the last two), how field of view and A* pathfinding hook into my own map type through two traits, how content lives in &lt;span class="caps"&gt;RON&lt;/span&gt; files instead of code, and how save games avoid serialising the &lt;span class="caps"&gt;ECS&lt;/span&gt; at&amp;nbsp;all.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 16 Aug 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-08-16:/crawlfest-building-a-terminal-roguelike-in-rust/</guid><category>Linux</category><category>rust</category><category>roguelike</category><category>gamedev</category><category>ratatui</category><category>ecs</category><category>legion</category><category>procedural-generation</category><category>field-of-view</category><category>pathfinding</category><category>serde</category><category>ron</category><category>terminal</category></item><item><title>Chezmoi and Git: Dotfiles Without Pretending Every Machine Is the Same</title><link>https://hofstede.it/chezmoi-and-git-dotfiles-without-pretending-every-machine-is-the-same/</link><description>&lt;p&gt;A Git repository is a good place for configuration files, but it does not know where they belong, which permissions they need, or why a work laptop and a home server should differ. Chezmoi adds that missing layer. This is how I use both tools to manage fish, Git, Neovim, GnuPG, OpenSSH and Atuin, including the recovery command for the inevitable day I edit a live file&amp;nbsp;directly.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Wed, 12 Aug 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-08-12:/chezmoi-and-git-dotfiles-without-pretending-every-machine-is-the-same/</guid><category>Linux</category><category>chezmoi</category><category>dotfiles</category><category>git</category><category>fish</category><category>neovim</category><category>gnupg</category><category>openssh</category><category>atuin</category><category>configuration-management</category><category>freebsd</category></item><item><title>Three Test Jails on a 512 MB Free-Tier VPS</title><link>https://hofstede.it/three-test-jails-on-a-512-mb-free-tier-vps/</link><description>&lt;p&gt;A bug report against my jailexec connection plugin needed a real FreeBSD jail to reproduce. An idle free-tier &lt;span class="caps"&gt;VPS&lt;/span&gt; with 512 &lt;span class="caps"&gt;MB&lt;/span&gt; of &lt;span class="caps"&gt;RAM&lt;/span&gt; turned out to be plenty: pkgbase provides a 33 &lt;span class="caps"&gt;MB&lt;/span&gt; base userland, persistent jails need no idle processes, and three Python-equipped test targets added only 1.1 &lt;span class="caps"&gt;GB&lt;/span&gt; of disk use. This is the build, including the two sharp edges that cost me twenty&amp;nbsp;minutes.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Tue, 04 Aug 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-08-04:/three-test-jails-on-a-512-mb-free-tier-vps/</guid><category>FreeBSD</category><category>freebsd</category><category>jails</category><category>pkgbase</category><category>ansible</category><category>jailexec</category><category>testing</category><category>vps</category><category>automation</category></item><item><title>Sane Development Environments for Ansible Automation Code</title><link>https://hofstede.it/sane-development-environments-for-ansible-automation-code/</link><description>&lt;p&gt;Ansible content deserves something better than a laptop full of loosely related pip packages. My preferred setup puts the editor on &lt;span class="caps"&gt;RHEL&lt;/span&gt;, the Red Hat-packaged Ansible toolchain in a versioned Dev Container, and Podman underneath both development and Execution Environment workflows. The result is reproducible without pretending that upstream community bits and supported downstream product content are the same&amp;nbsp;thing.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Mon, 03 Aug 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-08-03:/sane-development-environments-for-ansible-automation-code/</guid><category>Linux</category><category>ansible</category><category>ansible-automation-platform</category><category>ansible-dev-tools</category><category>vscode</category><category>dev-containers</category><category>podman</category><category>rhel</category><category>automation</category><category>development</category></item><item><title>Rice Deserves Better Than a Kochbeutel</title><link>https://hofstede.it/rice-deserves-better-than-a-kochbeutel/</link><description>&lt;p&gt;Rice is not the anonymous white ballast next to the actual food. Jasmine, basmati, brown rice, parboiled rice, and the great Italian risotto varieties all behave differently, and the way you cook them matters just as much. A short argument against the Kochbeutel, followed by the rice-cooker method that has served me&amp;nbsp;best.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 02 Aug 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-08-02:/rice-deserves-better-than-a-kochbeutel/</guid><category>Cooking</category><category>cooking</category><category>rice</category><category>recipe</category><category>off-topic</category></item><item><title>Running Your Own AS: An IXP over VXLAN, IPv4 on the Overlay, and a Config Spring Clean</title><link>https://hofstede.it/running-your-own-as-an-ixp-over-vxlan-ipv4-on-the-overlay-and-a-config-spring-clean/</link><description>&lt;p&gt;Part 5 of the &lt;span class="caps"&gt;AS201379&lt;/span&gt; journey: joining &lt;span class="caps"&gt;EVIX&lt;/span&gt;, an internet exchange that hands out &lt;span class="caps"&gt;VXLAN&lt;/span&gt; tunnels instead of switch ports, carrying a routed IPv4 /29 across the IPv6 overlay with &lt;span class="caps"&gt;PF&lt;/span&gt; policy routing, the dual-&lt;span class="caps"&gt;FIB&lt;/span&gt; routing that makes a &lt;span class="caps"&gt;VPS&lt;/span&gt; work as both a normal host and a routed &lt;span class="caps"&gt;AS&lt;/span&gt; site, moving the downstream MikroTik onto WireGuard, and a long-overdue cleanup of four routers&amp;#8217; worth of accumulated&amp;nbsp;configuration.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Thu, 30 Jul 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-07-30:/running-your-own-as-an-ixp-over-vxlan-ipv4-on-the-overlay-and-a-config-spring-clean/</guid><category>Networking</category><category>freebsd</category><category>bgp</category><category>networking</category><category>ipv6</category><category>ipv4</category><category>frr</category><category>pf</category><category>ixp</category><category>evix</category><category>vxlan</category><category>wireguard</category><category>policy-routing</category><category>jails</category><category>grafana</category></item><item><title>Building My Own TV Station: ErsatzTV in a FreeBSD Jail, With Intel Hardware Transcoding</title><link>https://hofstede.it/building-my-own-tv-station-ersatztv-in-a-freebsd-jail-with-intel-hardware-transcoding/</link><description>&lt;p&gt;Being ill for a week taught me that a large Jellyfin library is not entertainment, it is homework. ErsatzTV turns a media library back into linear television with real channels and schedules, but it only ships for Linux, Windows, and macOS. It is a .&lt;span class="caps"&gt;NET&lt;/span&gt; application driving ffmpeg, so I built it in a FreeBSD Bastille jail instead. One missing conditional was all that stood between FreeBSD and Intel &lt;span class="caps"&gt;VAAPI&lt;/span&gt; hardware&amp;nbsp;acceleration.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 26 Jul 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-07-26:/building-my-own-tv-station-ersatztv-in-a-freebsd-jail-with-intel-hardware-transcoding/</guid><category>FreeBSD</category><category>freebsd</category><category>bastille</category><category>jails</category><category>ersatztv</category><category>jellyfin</category><category>dotnet</category><category>ffmpeg</category><category>vaapi</category><category>i915kms</category><category>self-hosting</category><category>iptv</category></item><item><title>Android Development on Fedora 44 Without Installing an Android Development Stack</title><link>https://hofstede.it/android-development-on-fedora-44-without-installing-an-android-development-stack/</link><description>&lt;p&gt;I wanted to build a native Android companion for Kollect without filling Fedora 44 with a &lt;span class="caps"&gt;JDK&lt;/span&gt;, Gradle, Android SDKs, build tools, emulator images, and assorted mobile-development debris. My complete Android toolchain now lives in an Ubuntu 24.04 Distrobox instead. It builds the &lt;span class="caps"&gt;APK&lt;/span&gt;, talks to my phone over wireless &lt;span class="caps"&gt;ADB&lt;/span&gt;, runs the Android emulator, and even lets Kollect enrich links for free with Gemini Nano through Android&amp;nbsp;AICore.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Fri, 24 Jul 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-07-24:/android-development-on-fedora-44-without-installing-an-android-development-stack/</guid><category>Linux</category><category>android</category><category>fedora</category><category>distrobox</category><category>podman</category><category>kotlin</category><category>gradle</category><category>adb</category><category>android emulator</category><category>aicore</category><category>gemini nano</category><category>kollect</category></item><item><title>My Home Assistant Setup: bhyve, FreeBSD Jails, Zigbee, Homematic, and Matter over Thread</title><link>https://hofstede.it/my-home-assistant-setup-bhyve-freebsd-jails-zigbee-homematic-and-matter-over-thread/</link><description>&lt;p&gt;My Home Assistant &lt;span class="caps"&gt;OS&lt;/span&gt; installation runs as a bhyve &lt;span class="caps"&gt;VM&lt;/span&gt; on a FreeBSD home server, while Zigbee2MQTT and Mosquitto live in a &lt;span class="caps"&gt;VNET&lt;/span&gt; jail with direct access to a ConBee &lt;span class="caps"&gt;II&lt;/span&gt; &lt;span class="caps"&gt;USB&lt;/span&gt; adapter. Homematic comes through a &lt;span class="caps"&gt;CCU3&lt;/span&gt;, and three recent &lt;span class="caps"&gt;IKEA&lt;/span&gt; Matter-over-Thread devices use the Nanoleaf Shapes controller I already owned as their border&amp;nbsp;router.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sat, 18 Jul 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-07-18:/my-home-assistant-setup-bhyve-freebsd-jails-zigbee-homematic-and-matter-over-thread/</guid><category>FreeBSD</category><category>freebsd</category><category>home-assistant</category><category>bhyve</category><category>jails</category><category>zigbee2mqtt</category><category>mqtt</category><category>homematic</category><category>matter</category><category>thread</category><category>iot</category></item><item><title>Kollect: The Native KDE Link Collector I Built for Myself</title><link>https://hofstede.it/kollect-the-native-kde-link-collector-i-built-for-myself/</link><description>&lt;p&gt;Kollect is a small native Plasma 6 application I wrote to get interesting links out of browser tabs and into a durable collection. It uses Kirigami and C++ on the desktop, plain &lt;span class="caps"&gt;TOML&lt;/span&gt; files by default, optional multi-user server storage, OpenRouter-powered metadata, KWallet for secrets, and a proper Fedora &lt;span class="caps"&gt;RPM&lt;/span&gt;. The source is not public, but the design is worth&amp;nbsp;documenting.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Tue, 14 Jul 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-07-14:/kollect-the-native-kde-link-collector-i-built-for-myself/</guid><category>Linux</category><category>kde</category><category>plasma</category><category>kirigami</category><category>qt</category><category>cpp</category><category>fedora</category><category>rpm</category><category>fastapi</category><category>sqlite</category><category>openrouter</category><category>self-hosting</category></item><item><title>Hosting DokuWiki on FreeBSD with Bastille, nginx, and Caddy</title><link>https://hofstede.it/hosting-dokuwiki-on-freebsd-with-bastille-nginx-and-caddy/</link><description>&lt;p&gt;A small, database-free DokuWiki deployment in a FreeBSD 15.1 Bastille jail, with nginx and &lt;span class="caps"&gt;PHP&lt;/span&gt;-&lt;span class="caps"&gt;FPM&lt;/span&gt; inside the jail and Caddy handling &lt;span class="caps"&gt;TLS&lt;/span&gt; and access policy at the&amp;nbsp;edge.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Fri, 10 Jul 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-07-10:/hosting-dokuwiki-on-freebsd-with-bastille-nginx-and-caddy/</guid><category>FreeBSD</category><category>freebsd</category><category>bastille</category><category>jails</category><category>dokuwiki</category><category>nginx</category><category>caddy</category><category>php</category><category>self-hosting</category><category>ipv6</category></item><item><title>chana_masala.sh: A Recipe as a Shell Script</title><link>https://hofstede.it/chana_masalash-a-recipe-as-a-shell-script/</link><description>&lt;p&gt;Some years ago a chana masala arrived in a HelloFresh box and never left the household again. It has since been refactored, hardened, and put under version control. Here is the current release: a chickpea curry for hungry &lt;span class="caps"&gt;IT&lt;/span&gt; people, documented the only way I know how - as a bash script with a proper runbook&amp;nbsp;attached.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Tue, 07 Jul 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-07-07:/chana_masalash-a-recipe-as-a-shell-script/</guid><category>Cooking</category><category>cooking</category><category>recipe</category><category>bash</category><category>off-topic</category></item><item><title>A Caching FreeBSD Mirror for DN42: nginx proxy_store, pf, and a Dual-Homed VM</title><link>https://hofstede.it/a-caching-freebsd-mirror-for-dn42-nginx-proxy_store-pf-and-a-dual-homed-vm/</link><description>&lt;p&gt;Patching FreeBSD machines inside the &lt;span class="caps"&gt;DN42&lt;/span&gt; overlay network without giving them clearnet access - a dual-homed &lt;span class="caps"&gt;VM&lt;/span&gt; that lazily caches pkg.freebsd.org, update.freebsd.org, and release tarballs from ftp.freebsd.org with nginx proxy_store, follows &lt;span class="caps"&gt;CDN&lt;/span&gt; redirects server-side, and serves everything over IPv6 into the mesh. Now also available as a public &lt;span class="caps"&gt;DN42&lt;/span&gt; service at&amp;nbsp;bsdmirror.chofstede.dn42.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 05 Jul 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-07-05:/a-caching-freebsd-mirror-for-dn42-nginx-proxy_store-pf-and-a-dual-homed-vm/</guid><category>FreeBSD</category><category>freebsd</category><category>dn42</category><category>nginx</category><category>pf</category><category>caching</category><category>pkg</category><category>freebsd-update</category><category>ipv6</category></item><item><title>Upgrading FreeBSD 15.0-RELEASE to 15.1-RELEASE: The Official Paths</title><link>https://hofstede.it/upgrading-freebsd-150-release-to-151-release-the-official-paths/</link><description>&lt;p&gt;FreeBSD 15.1-&lt;span class="caps"&gt;RELEASE&lt;/span&gt; is here, and the official upgrade instructions depend on whether your system uses distribution sets or packaged base. This guide walks through both supported paths, covers the boot-loader update, and explains the configuration merging process - all based on the official 15.1 upgrading&amp;nbsp;documentation.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Wed, 01 Jul 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-07-01:/upgrading-freebsd-150-release-to-151-release-the-official-paths/</guid><category>FreeBSD</category><category>freebsd</category><category>upgrade</category><category>freebsd-update</category><category>pkgbase</category><category>bectl</category><category>boot-environments</category><category>zfs</category></item><item><title>FreeBSD Foundationals: The Boot Process - From the Loader to Boot Environments</title><link>https://hofstede.it/freebsd-foundationals-the-boot-process-from-the-loader-to-boot-environments/</link><description>&lt;p&gt;The third in the FreeBSD Foundationals series. This one covers how FreeBSD actually boots: the stages from power-on to login, &lt;span class="caps"&gt;BIOS&lt;/span&gt; vs &lt;span class="caps"&gt;UEFI&lt;/span&gt;, the loader and loader.conf, the difference between read-only tunables and runtime sysctls, the modern way to load kernel modules with kld_list, managing it all safely with sysrc, a practical security-hardening baseline, and - the headline act - boot environments with bectl, the undo button that turns a broken upgrade into a thirty-second&amp;nbsp;reboot.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Thu, 25 Jun 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-06-25:/freebsd-foundationals-the-boot-process-from-the-loader-to-boot-environments/</guid><category>FreeBSD</category><category>freebsd</category><category>boot</category><category>loader</category><category>loader.conf</category><category>kld_list</category><category>sysctl</category><category>sysrc</category><category>bectl</category><category>boot-environments</category><category>security</category><category>hardening</category></item><item><title>Monitoring a FreeBSD Mastodon Instance with Prometheus, Grafana, and Loki</title><link>https://hofstede.it/monitoring-a-freebsd-mastodon-instance-with-prometheus-grafana-and-loki/</link><description>&lt;p&gt;How I watch burningboard.net, my multi-jail FreeBSD Mastodon instance, from a separate observer host. A pull-based Prometheus stack reaching exporters across my own &lt;span class="caps"&gt;AS201379&lt;/span&gt; backbone (locked down at the perimeter firewall, not by binding to unroutable addresses), Loki and Promtail for nginx logs, a textfile collector that fills the gaps FreeBSD exporters leave (&lt;span class="caps"&gt;ZFS&lt;/span&gt;, S3, pkg audit, Mastodon &lt;span class="caps"&gt;API&lt;/span&gt; stats), one Grafana dashboard that tells me at a glance whether the instance is healthy, and an Alertmanager ruleset that emails me before users&amp;nbsp;notice.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 21 Jun 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-06-21:/monitoring-a-freebsd-mastodon-instance-with-prometheus-grafana-and-loki/</guid><category>FreeBSD</category><category>freebsd</category><category>mastodon</category><category>monitoring</category><category>observability</category><category>prometheus</category><category>grafana</category><category>loki</category><category>jails</category><category>ipv6</category></item><item><title>Leaving the Apple Ecosystem: One Fairphone Instead of Two iPhones</title><link>https://hofstede.it/leaving-the-apple-ecosystem-one-fairphone-instead-of-two-iphones/</link><description>&lt;p&gt;For years I carried two iPhones, a personal iPhone 12 and a work iPhone &lt;span class="caps"&gt;SE&lt;/span&gt;, and neither ever felt at home in my Linux and &lt;span class="caps"&gt;BSD&lt;/span&gt; centric life. I finally collapsed both into a single Fairphone Gen6 running Android with separate personal and work profiles. Here is why I picked the Fairphone, how Android slots into a desktop Linux workflow far better than iOS ever did, which apps I kept, which I swapped, why finally being able to read &lt;span class="caps"&gt;GPG&lt;/span&gt; encrypted mail on my phone is a real upgrade, and where the device falls&amp;nbsp;short.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Wed, 17 Jun 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-06-17:/leaving-the-apple-ecosystem-one-fairphone-instead-of-two-iphones/</guid><category>Hardware</category><category>android</category><category>fairphone</category><category>apple</category><category>fdroid</category><category>kde-connect</category><category>foss</category><category>self-hosting</category><category>repairability</category></item><item><title>IPv6 Foundations: The Internet Protocol You Should Already Be Using</title><link>https://hofstede.it/ipv6-foundations-the-internet-protocol-you-should-already-be-using/</link><description>&lt;p&gt;A laid-back tour through the basics of IPv6: how the addresses are built, how to shorten them without losing your mind, how they map onto the IPv4 you already know, and how hosts configure themselves with &lt;span class="caps"&gt;SLAAC&lt;/span&gt;. Plus a short sidebar on &lt;span class="caps"&gt;NDP&lt;/span&gt; and why blocking &lt;span class="caps"&gt;ICMP&lt;/span&gt; on an IPv6 network is a self-inflicted wound. The premise throughout: IPv6 is the current internet protocol, IPv4 is a relic we are still dragging around, and dual-stack is a burden, not a destination. Updated 2026-06-12 with reader Q&amp;amp;A on privacy addresses, banning abusive clients, &lt;span class="caps"&gt;NAT64&lt;/span&gt;/&lt;span class="caps"&gt;DNS64&lt;/span&gt;, and port&amp;nbsp;forwarding.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Mon, 08 Jun 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-06-08:/ipv6-foundations-the-internet-protocol-you-should-already-be-using/</guid><category>Networking</category><category>ipv6</category><category>networking</category><category>slaac</category><category>ndp</category><category>icmp</category><category>nat64</category><category>foundations</category></item><item><title>A Monoblock AC Is Only as Good as Its Window Seal</title><link>https://hofstede.it/a-monoblock-ac-is-only-as-good-as-its-window-seal/</link><description>&lt;p&gt;I moved into a top-floor 1970s apartment in one of the warmest corners of Germany, work from home, and needed the office to stay below &amp;#8220;thinking is hard now&amp;#8221;. A single-hose portable &lt;span class="caps"&gt;AC&lt;/span&gt; is a thermodynamically compromised machine, but most of what makes it bad happens at the window. Here is the personal story, a short detour into why these units leak, and the cheap &lt;span class="caps"&gt;XPS&lt;/span&gt; panel I cut to fix the part that actually&amp;nbsp;matters.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 07 Jun 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-06-07:/a-monoblock-ac-is-only-as-good-as-its-window-seal/</guid><category>DIY</category><category>diy</category><category>air conditioning</category><category>home</category><category>summer</category><category>off-topic</category></item><item><title>The AI Stack I Actually Run in 2026: A Laptop iGPU and Four Rented Frontiers</title><link>https://hofstede.it/ai-stack-2026/</link><description>&lt;p&gt;The most interesting thing about &lt;span class="caps"&gt;AI&lt;/span&gt; in 2026 is not which frontier model wins this month&amp;#8217;s benchmark. It is that the frontier became a commodity you rent through near-interchangeable clients, while the part with actual craft in it moved onto the integrated Radeon 780M in my laptop. Here is the tiered stack I actually run, with the local layer in detail because that is the unusual part, and the cloud layer kept brief because the pricing is on the vendors&amp;#8217; own pages and will be wrong by&amp;nbsp;autumn.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Wed, 03 Jun 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-06-03:/ai-stack-2026/</guid><category>Meta</category><category>ai</category><category>llm</category><category>mistral</category><category>gemma</category><category>lm-studio</category><category>amd</category><category>radeon</category><category>claude</category><category>glm</category><category>minimax</category><category>homelab</category></item><item><title>bcachefs on RHEL 10.2: The Kernel That Said No</title><link>https://hofstede.it/bcachefs-on-rhel-102-the-kernel-that-said-no/</link><description>&lt;p&gt;A few months ago I bullied &lt;span class="caps"&gt;RHEL&lt;/span&gt; onto a &lt;span class="caps"&gt;ZFS&lt;/span&gt; root and it worked. This time I tried to get bcachefs running on &lt;span class="caps"&gt;RHEL&lt;/span&gt; 10, lost a whole evening to compile errors, and the kernel won. Here is the autopsy, plus what bcachefs actually is and why an out-of-tree filesystem and a conservative enterprise kernel are a terrible&amp;nbsp;couple.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Mon, 01 Jun 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-06-01:/bcachefs-on-rhel-102-the-kernel-that-said-no/</guid><category>Linux</category><category>linux</category><category>rhel</category><category>bcachefs</category><category>dkms</category><category>kernel</category><category>fedora</category><category>unsupported</category></item><item><title>Two Sites, One Cluster: My Hetzner Proxmox VE Setup - A low-cost two-node cluster with VXLAN, ZFS replication and an external quorum vote</title><link>https://hofstede.it/hetzner-proxmox-cluster/</link><description>&lt;p&gt;How I run a single quorate Proxmox &lt;span class="caps"&gt;VE&lt;/span&gt; cluster across two cheap Hetzner dedicated servers in two different datacentres, glued together with Hetzner vSwitches, a &lt;span class="caps"&gt;VXLAN&lt;/span&gt; overlay, an external QDevice for quorum, and one OPNsense firewall per&amp;nbsp;node.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sat, 30 May 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-05-30:/hetzner-proxmox-cluster/</guid><category>Linux</category><category>proxmox</category><category>hetzner</category><category>vxlan</category><category>corosync</category><category>opnsense</category><category>bgp</category><category>networking</category><category>virtualization</category><category>self-hosting</category></item><item><title>Tag-Driven Deployments: How MastoSum Ships Itself with Forgejo Actions and Rootless Podman</title><link>https://hofstede.it/tag-driven-deployments-how-mastosum-ships-itself-with-forgejo-actions-and-rootless-podman/</link><description>&lt;p&gt;A walk through the MastoSum deployment pipeline: a version tag triggers Forgejo Actions, builds and signs a &lt;span class="caps"&gt;UBI&lt;/span&gt;-based image, then hands deployment to a rootless systemd/Podman host via a path unit and explicit cosign&amp;nbsp;verification.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 24 May 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-05-24:/tag-driven-deployments-how-mastosum-ships-itself-with-forgejo-actions-and-rootless-podman/</guid><category>Linux</category><category>forgejo</category><category>ci-cd</category><category>podman</category><category>quadlet</category><category>containers</category><category>deployment</category><category>cosign</category><category>ubi</category><category>redhat</category><category>systemd</category></item><item><title>mdo on FreeBSD 15: Base-System Privilege Delegation with mac_do</title><link>https://hofstede.it/mdo-on-freebsd-15-base-system-privilege-delegation-with-mac_do/</link><description>&lt;p&gt;FreeBSD 15&amp;nbsp;ships &lt;code&gt;mdo(1)&lt;/code&gt; and&amp;nbsp;the &lt;code&gt;mac_do(4)&lt;/code&gt; policy module in the base system. It&amp;nbsp;replaces &lt;code&gt;sudo&lt;/code&gt; and &lt;code&gt;doas&lt;/code&gt; for most of my hosts, needs no ports, and configures with a single sysctl. This article walks through enabling it, the rule syntax, a few real examples, and a short detour into the security sysctls I run on every&amp;nbsp;box.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Mon, 18 May 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-05-18:/mdo-on-freebsd-15-base-system-privilege-delegation-with-mac_do/</guid><category>FreeBSD</category><category>freebsd</category><category>security</category><category>mac</category><category>mac_do</category><category>privilege-delegation</category><category>sudo</category><category>doas</category><category>hardening</category><category>sysctl</category></item><item><title>Fedora Hummingbird: Distroless, Container-Native Linux and a Slim mastogreet</title><link>https://hofstede.it/fedora-hummingbird-distroless-container-native-linux-and-a-slim-mastogreet/</link><description>&lt;p&gt;Fedora Hummingbird brings the distroless container model to a full, image-based rolling operating system, and it ships a catalog of hardened language images alongside it. I rebuild the mastogreet bot&amp;#8217;s Containerfile on top&amp;nbsp;of &lt;code&gt;registry.access.redhat.com/hi/python&lt;/code&gt; to see what changes, what shrinks, and where the commercial Red Hat Hardened Images downstream fits&amp;nbsp;in.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sat, 16 May 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-05-16:/fedora-hummingbird-distroless-container-native-linux-and-a-slim-mastogreet/</guid><category>Linux</category><category>fedora</category><category>hummingbird</category><category>podman</category><category>containers</category><category>distroless</category><category>security</category><category>sbom</category><category>redhat</category><category>python</category></item><item><title>Red Hat Offline Knowledge Portal: All the Docs, Air-Gapped, On Your Laptop</title><link>https://hofstede.it/red-hat-offline-knowledge-portal-all-the-docs-air-gapped-on-your-laptop/</link><description>&lt;p&gt;The entire Red Hat documentation site and the full Knowledgebase fit into a single &lt;span class="caps"&gt;OCI&lt;/span&gt; container that updates weekly, runs locally with a web &lt;span class="caps"&gt;UI&lt;/span&gt; and Solr search, and is included in every &lt;span class="caps"&gt;RHEL&lt;/span&gt; subscription that bundles Satellite. I have it on my laptop. I use it daily. Almost nobody I talk to knows it exists. This post is my small contribution to fixing&amp;nbsp;that.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Thu, 14 May 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-05-14:/red-hat-offline-knowledge-portal-all-the-docs-air-gapped-on-your-laptop/</guid><category>Linux</category><category>red hat</category><category>rhel</category><category>satellite</category><category>documentation</category><category>offline</category><category>air-gap</category><category>podman</category><category>containers</category><category>knowledge-base</category></item><item><title>A Field Manual for Three Years on Deutsche Bahn</title><link>https://hofstede.it/a-field-manual-for-three-years-on-deutsche-bahn/</link><description>&lt;p&gt;After years of regular business travel by Deutsche Bahn, here is the small library of habits, app picks, routing folklore, and survival gear that actually helps. Not a complaint piece. A handbook for everyone who has resigned themselves to the system and would like the next trip to suck a little&amp;nbsp;less.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Wed, 13 May 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-05-13:/a-field-manual-for-three-years-on-deutsche-bahn/</guid><category>Travel</category><category>travel</category><category>deutsche bahn</category><category>consulting</category><category>off-topic</category></item><item><title>FreeBSD Resource Monitoring, Accounting, and Troubleshooting</title><link>https://hofstede.it/freebsd-resource-monitoring-accounting-and-troubleshooting/</link><description>&lt;p&gt;A practical tour of FreeBSD&amp;#8217;s built-in tools for watching &lt;span class="caps"&gt;CPU&lt;/span&gt;, memory, disk I/O, and network activity, finding the process or jail that is eating your server, and applying per-jail accounting and limits with kern.racct and&amp;nbsp;rctl.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Tue, 12 May 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-05-12:/freebsd-resource-monitoring-accounting-and-troubleshooting/</guid><category>FreeBSD</category><category>freebsd</category><category>performance</category><category>monitoring</category><category>troubleshooting</category><category>jails</category><category>racct</category><category>rctl</category><category>sysctl</category><category>network</category><category>observability</category></item><item><title>Distrobox: Different Distributions in a Box, Powered by Podman</title><link>https://hofstede.it/distrobox-different-distributions-in-a-box-powered-by-podman/</link><description>&lt;p&gt;A &amp;#8220;real&amp;#8221; &lt;span class="caps"&gt;RHEL&lt;/span&gt; container on a Fedora laptop, an Arch box for the &lt;span class="caps"&gt;AUR&lt;/span&gt;, an Ubuntu box for that one vendor tool that ships .deb files only, all of them with your home directory mounted, your shell history shared, and &lt;span class="caps"&gt;GUI&lt;/span&gt; apps that integrate into your desktop as if they were native. Distrobox uses Podman to make that boring instead of clever, and it pairs especially well with Atomic distributions where the host is meant to stay&amp;nbsp;immutable.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 10 May 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-05-10:/distrobox-different-distributions-in-a-box-powered-by-podman/</guid><category>Linux</category><category>distrobox</category><category>podman</category><category>containers</category><category>linux</category><category>fedora</category><category>rhel</category><category>silverblue</category><category>kinoite</category><category>atomic</category><category>btrfs</category><category>vscode</category><category>development</category></item><item><title>Reproducible Ansible with Execution Environments</title><link>https://hofstede.it/reproducible-ansible-with-execution-environments/</link><description>&lt;p&gt;A &amp;#8220;control node&amp;#8221; with a hand-curated venv works. Until it doesn&amp;#8217;t. A colleague has different collection versions, &lt;span class="caps"&gt;CI&lt;/span&gt; installs a slightly newer Python library, and a playbook that ran yesterday now fails. Execution Environments turn the control node into a versioned container image. ansible-builder produces it, ansible-navigator runs against it, and the same artifact ships from your laptop into &lt;span class="caps"&gt;AAP&lt;/span&gt;/&lt;span class="caps"&gt;AWX&lt;/span&gt; without&amp;nbsp;modification.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Wed, 06 May 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-05-06:/reproducible-ansible-with-execution-environments/</guid><category>Linux</category><category>ansible</category><category>execution-environments</category><category>ansible-builder</category><category>ansible-navigator</category><category>containers</category><category>podman</category><category>automation</category><category>rhel</category></item><item><title>Ansible-Native Quadlets: Deploying a Mastodon Greeter Bot with containers.podman</title><link>https://hofstede.it/ansible-native-quadlets-deploying-a-mastodon-greeter-bot-with-containerspodman/</link><description>&lt;p&gt;Hand-writing Quadlet files works for one host. For a fleet, the containers.podman collection&amp;#8217;s native Quadlet generation lets you describe containers as Ansible state, including secrets, registry logins, and templated configuration. A small Mastodon welcome bot makes a concrete&amp;nbsp;example.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Mon, 27 Apr 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-04-27:/ansible-native-quadlets-deploying-a-mastodon-greeter-bot-with-containerspodman/</guid><category>Linux</category><category>ansible</category><category>podman</category><category>quadlet</category><category>containers</category><category>systemd</category><category>mastodon</category><category>automation</category><category>rhel</category></item><item><title>Joining DN42: A MikroTik Border, Three WireGuard Peerings, and a FreeBSD Jail in the Hobbyist Internet</title><link>https://hofstede.it/joining-dn42-a-mikrotik-border-three-wireguard-peerings-and-a-freebsd-jail-in-the-hobbyist-internet/</link><description>&lt;p&gt;Building a &lt;span class="caps"&gt;DN42&lt;/span&gt; node from scratch - registering &lt;span class="caps"&gt;AS4242422539&lt;/span&gt; and fdce:73f7:a2dc::/48 in the registry, configuring a MikroTik border router with three WireGuard peerings and &lt;span class="caps"&gt;BGP&lt;/span&gt; filters, running a FreeBSD bastille jail as authoritative &lt;span class="caps"&gt;DNS&lt;/span&gt; for chofstede.dn42, and reaching the rest of the hobbyist mesh in two&amp;nbsp;hops.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Fri, 24 Apr 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-04-24:/joining-dn42-a-mikrotik-border-three-wireguard-peerings-and-a-freebsd-jail-in-the-hobbyist-internet/</guid><category>Networking</category><category>dn42</category><category>bgp</category><category>networking</category><category>ipv6</category><category>mikrotik</category><category>routeros</category><category>wireguard</category><category>freebsd</category><category>bastille</category><category>powerdns</category></item><item><title>Running Your Own AS: Direct Hetzner Peering, a Fourth Edge, and Bringing the Home LAN into the Fabric</title><link>https://hofstede.it/running-your-own-as-direct-hetzner-peering-a-fourth-edge-and-bringing-the-home-lan-into-the-fabric/</link><description>&lt;p&gt;Part 4 of the &lt;span class="caps"&gt;AS201379&lt;/span&gt; journey: adding a fourth FreeBSD edge router at iFog with FogIXP peering, establishing direct &lt;span class="caps"&gt;BGP&lt;/span&gt; sessions with Hetzner, bringing the home network into the &lt;span class="caps"&gt;AS&lt;/span&gt; via an iBGP-speaking MikroTik, and a little traffic engineering to steer Deutsche Telekom traffic over&amp;nbsp;Vultr.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Thu, 16 Apr 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-04-16:/running-your-own-as-direct-hetzner-peering-a-fourth-edge-and-bringing-the-home-lan-into-the-fabric/</guid><category>Networking</category><category>freebsd</category><category>bgp</category><category>networking</category><category>ipv6</category><category>frr</category><category>pf</category><category>ibgp</category><category>ixp</category><category>mikrotik</category><category>routeros</category></item><item><title>Automating FreeBSD Jails with cdist - Zero Dependencies Inside the Jail</title><link>https://hofstede.it/automating-freebsd-jails-with-cdist-zero-dependencies-inside-the-jail/</link><description>&lt;p&gt;cdist is refreshingly minimal - the target only needs &lt;span class="caps"&gt;POSIX&lt;/span&gt; sh, and the control machine speaks ssh. But cdist expects one ssh endpoint per host, and FreeBSD jails are not normally their own ssh targets. Two small Python wrappers plug cdist into jexec on the host, so configuration state flows into every jail without running a single daemon, agent, or Python interpreter inside the jail&amp;nbsp;itself.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 12 Apr 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-04-12:/automating-freebsd-jails-with-cdist-zero-dependencies-inside-the-jail/</guid><category>FreeBSD</category><category>freebsd</category><category>jails</category><category>cdist</category><category>automation</category><category>devops</category><category>unix-philosophy</category><category>jexec</category></item><item><title>Replacing Lenovo’s WWAN Unlock Blob with a 100-Line Bash Script</title><link>https://hofstede.it/replacing-lenovos-wwan-unlock-blob-with-a-100-line-bash-script/</link><description>&lt;p&gt;My ThinkPad T14s shipped with an Intel &lt;span class="caps"&gt;XMM7560&lt;/span&gt; &lt;span class="caps"&gt;LTE&lt;/span&gt; modem that would not register on the network until Lenovo&amp;#8217;s proprietary &lt;span class="caps"&gt;FCC&lt;/span&gt;-unlock helper ran. I replaced it with a roughly 100-line bash script from a ModemManager merge request, and along the way learned that the &amp;#8220;unlock&amp;#8221; is just a small challenge-response handshake that is easy to explain in plain&amp;nbsp;shell.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sat, 11 Apr 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-04-11:/replacing-lenovos-wwan-unlock-blob-with-a-100-line-bash-script/</guid><category>Linux</category><category>linux</category><category>fedora</category><category>hardware</category><category>modemmanager</category><category>lte</category><category>wwan</category><category>foss</category><category>thinkpad</category></item><item><title>Podman on FreeBSD: OCI Containers Without systemd</title><link>https://hofstede.it/podman-on-freebsd-oci-containers-without-systemd/</link><description>&lt;p&gt;Podman runs on FreeBSD too - but without systemd, the workflow is different. This follow-up to my Linux Podman deep dive covers how to run both native FreeBSD and Linux &lt;span class="caps"&gt;OCI&lt;/span&gt; containers on FreeBSD, how container lifecycle management works without Quadlets, and how Podman complements Jails rather than replacing&amp;nbsp;them.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Mon, 06 Apr 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-04-06:/podman-on-freebsd-oci-containers-without-systemd/</guid><category>FreeBSD</category><category>freebsd</category><category>podman</category><category>containers</category><category>oci</category><category>jails</category><category>linuxulator</category><category>docker</category></item><item><title>Podman in Production: Quadlets, Secrets, Auto-Updates, and Docker Compatibility</title><link>https://hofstede.it/podman-in-production-quadlets-secrets-auto-updates-and-docker-compatibility/</link><description>&lt;p&gt;An opinionated production-ops guide to Podman on Linux servers - why I prefer it over Docker, how Quadlets replace Compose files, and practical patterns from real deployments including secrets management, auto-updates, and Docker&amp;nbsp;compatibility.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 05 Apr 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-04-05:/podman-in-production-quadlets-secrets-auto-updates-and-docker-compatibility/</guid><category>Linux</category><category>podman</category><category>containers</category><category>quadlet</category><category>systemd</category><category>linux</category><category>rhel</category><category>docker</category><category>secrets</category><category>traefik</category></item><item><title>Speeding Up Forgejo CI with a Custom OCI Image</title><link>https://hofstede.it/speeding-up-forgejo-ci-with-a-custom-oci-image/</link><description>&lt;p&gt;How I cut my blog&amp;#8217;s &lt;span class="caps"&gt;CI&lt;/span&gt;/&lt;span class="caps"&gt;CD&lt;/span&gt; build time in half by baking dependencies into a custom container image and hosting it in Forgejo&amp;#8217;s built-in &lt;span class="caps"&gt;OCI&lt;/span&gt;&amp;nbsp;registry.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Wed, 01 Apr 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-04-01:/speeding-up-forgejo-ci-with-a-custom-oci-image/</guid><category>Meta</category><category>forgejo</category><category>ci-cd</category><category>containers</category><category>oci</category><category>pelican</category><category>devops</category></item><item><title>Keycloak 26 on Podman with Quadlets: Identity Management the systemd Way</title><link>https://hofstede.it/keycloak-26-on-podman-with-quadlets-identity-management-the-systemd-way/</link><description>&lt;p&gt;Deploying Keycloak 26 as an identity provider using Podman Quadlets with network segmentation, secret management, and systemd&amp;nbsp;integration.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Tue, 31 Mar 2026 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2026-03-31:/keycloak-26-on-podman-with-quadlets-identity-management-the-systemd-way/</guid><category>Linux</category><category>linux</category><category>podman</category><category>containers</category><category>quadlet</category><category>systemd</category><category>keycloak</category><category>identity</category><category>rhel</category></item><item><title>My Multi-Stage Backup Strategy: ZFS, Proxmox, and Paranoia</title><link>https://hofstede.it/my-multi-stage-backup-strategy-zfs-proxmox-and-paranoia/</link><description>&lt;p&gt;Backups are the thing everyone knows they should do and nobody does well enough. Here&amp;#8217;s my multi-stage strategy for keeping about a dozen servers safe: &lt;span class="caps"&gt;ZFS&lt;/span&gt; snapshots with sanoid, off-site replication with syncoid to rsync.net, Proxmox Backup Server with an S3 backend for VMs, and a creative Podman trick for backing up &lt;span class="caps"&gt;RHEL&lt;/span&gt; hosts that don&amp;#8217;t have proxmox-backup-client. Plus a dead man&amp;#8217;s switch, because the only thing worse than no backups is backups that silently stopped working three months&amp;nbsp;ago.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sat, 28 Mar 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-03-28:/my-multi-stage-backup-strategy-zfs-proxmox-and-paranoia/</guid><category>Linux</category><category>backup</category><category>zfs</category><category>freebsd</category><category>linux</category><category>proxmox</category><category>sanoid</category><category>syncoid</category><category>rsync</category><category>podman</category><category>infrastructure</category></item><item><title>Shell Tricks That Actually Make Life Easier (And Save Your Sanity)</title><link>https://hofstede.it/shell-tricks-that-actually-make-life-easier-and-save-your-sanity/</link><description>&lt;p&gt;Watch someone backspace 40 characters instead of pressing &lt;span class="caps"&gt;CTRL&lt;/span&gt;+W, and you&amp;#8217;ll understand why this list exists. A collection of shell tricks-grouped by what works everywhere and what&amp;#8217;s Bash/Zsh-specific-that save keystrokes and&amp;nbsp;time.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Thu, 26 Mar 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-03-26:/shell-tricks-that-actually-make-life-easier-and-save-your-sanity/</guid><category>Unix</category><category>shell</category><category>bash</category><category>unix</category><category>sysadmin</category><category>freebsd</category><category>linux</category></item><item><title>Dual-FIB Policy Routing on FreeBSD: Two Upstreams, One Server, Zero Confusion</title><link>https://hofstede.it/dual-fib-policy-routing-on-freebsd-two-upstreams-one-server-zero-confusion/</link><description>&lt;p&gt;How to run a FreeBSD server with two completely independent internet uplinks - a physical provider and a &lt;span class="caps"&gt;BGP&lt;/span&gt; tunnel - using dual-&lt;span class="caps"&gt;FIB&lt;/span&gt; routing tables, &lt;span class="caps"&gt;PF&lt;/span&gt;&amp;#8217;s rtable and reply-to directives, and a single bridge that carries &lt;span class="caps"&gt;NAT&lt;/span&gt;&amp;#8217;d, routed, and pure public jail traffic&amp;nbsp;simultaneously.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Mon, 23 Mar 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-03-23:/dual-fib-policy-routing-on-freebsd-two-upstreams-one-server-zero-confusion/</guid><category>FreeBSD</category><category>freebsd</category><category>networking</category><category>pf</category><category>bgp</category><category>jails</category><category>tunneling</category><category>policy-routing</category></item><item><title>Running Your Own AS: Joining an IXP with a Third Edge Router</title><link>https://hofstede.it/running-your-own-as-joining-an-ixp-with-a-third-edge-router/</link><description>&lt;p&gt;Connecting &lt;span class="caps"&gt;AS201379&lt;/span&gt; to LocIX Düsseldorf via a dedicated edge router - adding direct exchange point peering to the existing multi-homed &lt;span class="caps"&gt;BGP&lt;/span&gt; setup, completing a three-router FreeBSD infrastructure with transit, native peering, and &lt;span class="caps"&gt;IXP&lt;/span&gt;&amp;nbsp;connectivity.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sat, 21 Mar 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-03-21:/running-your-own-as-joining-an-ixp-with-a-third-edge-router/</guid><category>Networking</category><category>freebsd</category><category>bgp</category><category>networking</category><category>ipv6</category><category>frr</category><category>pf</category><category>ixp</category><category>locix</category><category>ibgp</category></item><item><title>Why I Prefer CentOS Stream Over Old CentOS</title><link>https://hofstede.it/why-i-prefer-centos-stream-over-old-centos/</link><description>&lt;p&gt;Old CentOS rebuilt &lt;span class="caps"&gt;RHEL&lt;/span&gt; faithfully, but its downstream position meant it could only follow, never contribute back. CentOS Stream changes that. Sitting upstream of &lt;span class="caps"&gt;RHEL&lt;/span&gt; and downstream of Fedora, it combines enterprise-grade stability with a genuine feedback loop into &lt;span class="caps"&gt;RHEL&lt;/span&gt; development. After years of running it in production, I&amp;#8217;m convinced it&amp;#8217;s the better&amp;nbsp;model.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 15 Mar 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-03-15:/why-i-prefer-centos-stream-over-old-centos/</guid><category>Linux</category><category>linux</category><category>centos</category><category>centos-stream</category><category>rhel</category><category>fedora</category><category>server</category><category>enterprise</category></item><item><title>Linux Firewalls: How to Actually Secure a Cloud Server (iptables, nftables, firewalld, ufw)</title><link>https://hofstede.it/linux-firewalls-how-to-actually-secure-a-cloud-server-iptables-nftables-firewalld-ufw/</link><description>&lt;p&gt;A practical guide to the four major Linux firewall technologies - iptables, nftables, firewalld, and ufw. Covers real-world cloud server hardening with concrete examples, from locking down &lt;span class="caps"&gt;SSH&lt;/span&gt; to building zone-based configurations. Includes an honest comparison and an entirely unbiased opinion about which firewall is actually&amp;nbsp;best.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sat, 14 Mar 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-03-14:/linux-firewalls-how-to-actually-secure-a-cloud-server-iptables-nftables-firewalld-ufw/</guid><category>Linux</category><category>linux</category><category>firewall</category><category>iptables</category><category>nftables</category><category>firewalld</category><category>ufw</category><category>security</category><category>networking</category><category>cloud</category></item><item><title>FreeBSD Foundationals: ZFS - The Last Filesystem You’ll Ever Need</title><link>https://hofstede.it/freebsd-foundationals-zfs-the-last-filesystem-youll-ever-need/</link><description>&lt;p&gt;The second in the FreeBSD Foundationals series. This one covers &lt;span class="caps"&gt;ZFS&lt;/span&gt; from philosophy to practice: why it exists, how pools and datasets work, what checksumming and self-healing actually do, how to tune recordsize, compression, and atime, how encryption works with key management, how snapshots and the hidden .zfs directory give you time travel, and how &lt;span class="caps"&gt;ZFS&lt;/span&gt; send/recv turns backup and migration into a solved problem. Includes a look at sanoid/syncoid for automated snapshot&amp;nbsp;management.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Fri, 13 Mar 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-03-13:/freebsd-foundationals-zfs-the-last-filesystem-youll-ever-need/</guid><category>FreeBSD</category><category>freebsd</category><category>zfs</category><category>filesystem</category><category>storage</category><category>encryption</category><category>backup</category><category>snapshots</category><category>sanoid</category></item><item><title>FreeBSD Foundationals: Jails - From Chroot on Steroids to Full Virtual Networks</title><link>https://hofstede.it/freebsd-foundationals-jails-from-chroot-on-steroids-to-full-virtual-networks/</link><description>&lt;p&gt;The first in a series on FreeBSD fundamentals. This one covers Jails from the ground up: why they exist, how classic Jails differ from &lt;span class="caps"&gt;VNET&lt;/span&gt; Jails, what epair interfaces actually are, how bridges tie it all together, and what devfs rules do for your isolation story. Practical configurations&amp;nbsp;included.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Mon, 02 Mar 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-03-02:/freebsd-foundationals-jails-from-chroot-on-steroids-to-full-virtual-networks/</guid><category>FreeBSD</category><category>freebsd</category><category>jails</category><category>vnet</category><category>networking</category><category>containers</category><category>isolation</category><category>security</category><category>pf</category></item><item><title>Neovim Crash Course for Sysadmins: The 20% That Solve 80% of the Pain</title><link>https://hofstede.it/neovim-crash-course-for-sysadmins-the-20-that-solve-80-of-the-pain/</link><description>&lt;p&gt;Not another hjkl tutorial. This is the stuff you still get wrong after years of using Vim - efficient navigation, copy/paste that actually works, &lt;span class="caps"&gt;YAML&lt;/span&gt;-specific workflows, and the motions that turn config file editing from a chore into a&amp;nbsp;joy.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Fri, 27 Feb 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-02-27:/neovim-crash-course-for-sysadmins-the-20-that-solve-80-of-the-pain/</guid><category>Linux</category><category>neovim</category><category>vim</category><category>sysadmin</category><category>devops</category><category>yaml</category><category>ansible</category><category>productivity</category></item><item><title>Running Your Own AS: Going Multi-Homed with iBGP and three Transits</title><link>https://hofstede.it/running-your-own-as-going-multi-homed-with-ibgp-and-three-transits/</link><description>&lt;p&gt;Expanding a single &lt;span class="caps"&gt;BGP&lt;/span&gt; router into a two-PoP distributed network: adding a Vultr edge router with native &lt;span class="caps"&gt;BGP&lt;/span&gt; peering, three upstream &lt;span class="caps"&gt;GRE&lt;/span&gt; providers and iBGP to tie it together - plus the stateless &lt;span class="caps"&gt;PF&lt;/span&gt; rules that make transit routing actually&amp;nbsp;work.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Thu, 26 Feb 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-02-26:/running-your-own-as-going-multi-homed-with-ibgp-and-three-transits/</guid><category>Networking</category><category>freebsd</category><category>bgp</category><category>networking</category><category>ipv6</category><category>frr</category><category>pf</category><category>ibgp</category><category>multihoming</category></item><item><title>HTTP/3 on FreeBSD: Getting QUIC Working with nginx in a Bastille Jail</title><link>https://hofstede.it/http3-on-freebsd-getting-quic-working-with-nginx-in-a-bastille-jail/</link><description>&lt;p&gt;What looked like a simple nginx config change turned into a tour through &lt;span class="caps"&gt;SSL&lt;/span&gt; library incompatibilities, pf firewall rules for a new protocol, and a multi-worker affinity problem that only shows up under real traffic. A complete guide to getting &lt;span class="caps"&gt;HTTP&lt;/span&gt;/3 working with nginx 1.28 on FreeBSD 15.0 inside a Bastille&amp;nbsp;jail.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sat, 21 Feb 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-02-21:/http3-on-freebsd-getting-quic-working-with-nginx-in-a-bastille-jail/</guid><category>FreeBSD</category><category>freebsd</category><category>nginx</category><category>http3</category><category>quic</category><category>networking</category><category>jails</category><category>bastille</category></item><item><title>Integrating LaCrosse Sensors into Home Assistant via JeeLink on FreeBSD</title><link>https://hofstede.it/integrating-lacrosse-sensors-into-home-assistant-via-jeelink-on-freebsd/</link><description>&lt;p&gt;Using a JeeLink &lt;span class="caps"&gt;USB&lt;/span&gt; stick inside a FreeBSD jail to bridge legacy LaCrosse temperature and humidity sensors to Home Assistant over &lt;span class="caps"&gt;MQTT&lt;/span&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Thu, 19 Feb 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-02-19:/integrating-lacrosse-sensors-into-home-assistant-via-jeelink-on-freebsd/</guid><category>FreeBSD</category><category>freebsd</category><category>jails</category><category>home-assistant</category><category>mqtt</category><category>iot</category><category>sensors</category></item><item><title>RHEL on ZFS Root: An Unholy Experiment</title><link>https://hofstede.it/rhel-on-zfs-root-an-unholy-experiment/</link><description>&lt;p&gt;Running Red Hat Enterprise Linux on &lt;span class="caps"&gt;ZFS&lt;/span&gt; root is not supported. I did it anyway. Here&amp;#8217;s how this cursed configuration came to be, why you shouldn&amp;#8217;t replicate it, and what the proper alternative looks&amp;nbsp;like.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sat, 14 Feb 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-02-14:/rhel-on-zfs-root-an-unholy-experiment/</guid><category>Linux</category><category>linux</category><category>rhel</category><category>zfs</category><category>rocky</category><category>convert2rhel</category><category>unsupported</category></item><item><title>SELinux: A Practical Guide for Fedora and RHEL</title><link>https://hofstede.it/selinux-a-practical-guide-for-fedora-and-rhel/</link><description>&lt;p&gt;Moving beyond &amp;#8220;setenforce 0&amp;#8221; - a practical guide to understanding, troubleshooting, and working with SELinux on Fedora and Red Hat Enterprise&amp;nbsp;Linux.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Fri, 13 Feb 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-02-13:/selinux-a-practical-guide-for-fedora-and-rhel/</guid><category>Linux</category><category>linux</category><category>fedora</category><category>rhel</category><category>selinux</category><category>security</category><category>containers</category><category>podman</category></item><item><title>Podman 5.8: Quadlet Multi-File Install, Automatic SQLite Migration, and the Road to 6.0</title><link>https://hofstede.it/podman-58-quadlet-multi-file-install-automatic-sqlite-migration-and-the-road-to-60/</link><description>&lt;p&gt;Podman 5.8 lands with multi-file Quadlet installs, automatic BoltDB-to-SQLite migration in preparation for Podman 6.0, and several quality-of-life improvements for container&amp;nbsp;workflows.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Thu, 12 Feb 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-02-12:/podman-58-quadlet-multi-file-install-automatic-sqlite-migration-and-the-road-to-60/</guid><category>Linux</category><category>podman</category><category>containers</category><category>quadlet</category><category>systemd</category><category>linux</category><category>rhel</category><category>sqlite</category></item><item><title>Adding Fediverse Comments to a Pelican Blog</title><link>https://hofstede.it/adding-fediverse-comments-to-a-pelican-blog/</link><description>&lt;p&gt;How I added a Mastodon-based comment system to this Pelican blog - no databases, no third-party services, just the Fediverse&amp;#8217;s public &lt;span class="caps"&gt;API&lt;/span&gt; and a bit of&amp;nbsp;JavaScript.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Tue, 10 Feb 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-02-10:/adding-fediverse-comments-to-a-pelican-blog/</guid><category>Meta</category><category>pelican</category><category>fediverse</category><category>mastodon</category><category>activitypub</category><category>blog</category><category>javascript</category></item><item><title>Running Your Own AS: BGP on FreeBSD with FRR, GRE Tunnels, and Policy Routing</title><link>https://hofstede.it/running-your-own-as-bgp-on-freebsd-with-frr-gre-tunnels-and-policy-routing/</link><description>&lt;p&gt;How I obtained my own &lt;span class="caps"&gt;AS&lt;/span&gt; number and IPv6 prefix, set up a FreeBSD &lt;span class="caps"&gt;BGP&lt;/span&gt; router with &lt;span class="caps"&gt;FRR&lt;/span&gt;, and built a tunnel overlay to bring globally routable addresses to servers that already have provider-assigned IPv6 - using dual-&lt;span class="caps"&gt;FIB&lt;/span&gt; policy routing to make both&amp;nbsp;coexist.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 08 Feb 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-02-08:/running-your-own-as-bgp-on-freebsd-with-frr-gre-tunnels-and-policy-routing/</guid><category>Networking</category><category>freebsd</category><category>bgp</category><category>networking</category><category>ipv6</category><category>frr</category><category>pf</category><category>tunneling</category></item><item><title>PF Firewall on FreeBSD: A Practical Guide</title><link>https://hofstede.it/pf-firewall-on-freebsd-a-practical-guide/</link><description>&lt;p&gt;A comprehensive guide to configuring &lt;span class="caps"&gt;PF&lt;/span&gt; on FreeBSD, covering core concepts, practical configurations for jails and dual-stack networking, and advanced techniques including brute-force protection and bastion host setups with&amp;nbsp;authpf.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Fri, 06 Feb 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-02-06:/pf-firewall-on-freebsd-a-practical-guide/</guid><category>FreeBSD</category><category>freebsd</category><category>firewall</category><category>pf</category><category>security</category><category>networking</category></item><item><title>Immutable Linux Desktops: Universal Blue, OSTree, and the Future of Desktop Linux</title><link>https://hofstede.it/immutable-linux-desktops-universal-blue-ostree-and-the-future-of-desktop-linux/</link><description>&lt;p&gt;Exploring atomic desktop Linux distributions, the technology stack behind them, and why Universal Blue&amp;#8217;s Aurora and Bazzite represent a compelling vision for reliable, maintainable desktop&amp;nbsp;systems.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Mon, 26 Jan 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-01-26:/immutable-linux-desktops-universal-blue-ostree-and-the-future-of-desktop-linux/</guid><category>Linux</category><category>linux</category><category>fedora</category><category>ostree</category><category>rpm-ostree</category><category>bootc</category><category>universal-blue</category><category>aurora</category><category>bazzite</category><category>atomic</category></item><item><title>Integrating FreeBSD 15 with FreeIPA: Native Kerberos and LDAP Authentication</title><link>https://hofstede.it/integrating-freebsd-15-with-freeipa-native-kerberos-and-ldap-authentication/</link><description>&lt;p&gt;A clean approach to integrating FreeBSD 15 into a FreeIPA realm using native components - Kerberos for authentication, &lt;span class="caps"&gt;LDAP&lt;/span&gt; for identity, and no local user&amp;nbsp;management.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 25 Jan 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-01-25:/integrating-freebsd-15-with-freeipa-native-kerberos-and-ldap-authentication/</guid><category>FreeBSD</category><category>freebsd</category><category>freeipa</category><category>kerberos</category><category>ldap</category><category>authentication</category><category>security</category></item><item><title>Reviving Life is Strange: Before the Storm on Modern Linux with a glibc Shim</title><link>https://hofstede.it/reviving-life-is-strange-before-the-storm-on-modern-linux-with-a-glibc-shim/</link><description>&lt;p&gt;Fixing Life is Strange Before the Storm on modern Linux distributions by compiling a small shim library that restores deprecated glibc internal&amp;nbsp;functions.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 25 Jan 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-01-25:/reviving-life-is-strange-before-the-storm-on-modern-linux-with-a-glibc-shim/</guid><category>Linux</category><category>linux</category><category>gaming</category><category>steam</category><category>fedora</category><category>glibc</category><category>linuxgaming</category></item><item><title>Self-Hosted CryptPad on FreeBSD with VNET Jails and Caddy</title><link>https://hofstede.it/self-hosted-cryptpad-on-freebsd-with-vnet-jails-and-caddy/</link><description>&lt;p&gt;Running CryptPad in a FreeBSD &lt;span class="caps"&gt;VNET&lt;/span&gt; jail with isolated networking, &lt;span class="caps"&gt;NAT&lt;/span&gt; via &lt;span class="caps"&gt;PF&lt;/span&gt;, and Caddy for &lt;span class="caps"&gt;TLS&lt;/span&gt;&amp;nbsp;termination.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sat, 24 Jan 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-01-24:/self-hosted-cryptpad-on-freebsd-with-vnet-jails-and-caddy/</guid><category>FreeBSD</category><category>freebsd</category><category>jails</category><category>self-hosting</category><category>privacy</category></item><item><title>Self-Hosting Email on FreeBSD: A Secure, Jailed Setup with Postfix and Dovecot</title><link>https://hofstede.it/self-hosting-email-on-freebsd-a-secure-jailed-setup-with-postfix-and-dovecot/</link><description>&lt;p&gt;A technical deep-dive into running a modern, secure mail server on FreeBSD 15.0 using &lt;span class="caps"&gt;VNET&lt;/span&gt; jails, &lt;span class="caps"&gt;ZFS&lt;/span&gt; encryption, and GeoIP-aware&amp;nbsp;firewalling.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 18 Jan 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-01-18:/self-hosting-email-on-freebsd-a-secure-jailed-setup-with-postfix-and-dovecot/</guid><category>FreeBSD</category><category>freebsd</category><category>mail</category><category>postfix</category><category>dovecot</category><category>rspamd</category><category>jails</category><category>zfs</category><category>security</category></item><item><title>Card Wars: Hiding Smartcard Readers from Eager Rust Agents with LD_PRELOAD</title><link>https://hofstede.it/card-wars-hiding-smartcard-readers-from-eager-rust-agents-with-ld_preload/</link><description>&lt;p&gt;Using LD_PRELOAD to surgically hide a &lt;span class="caps"&gt;PC&lt;/span&gt;/&lt;span class="caps"&gt;SC&lt;/span&gt; smartcard reader from a Rust-based OpenPGP &lt;span class="caps"&gt;SSH&lt;/span&gt; agent, allowing two incompatible hardware security stacks to coexist peacefully on the same&amp;nbsp;system.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sat, 17 Jan 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-01-17:/card-wars-hiding-smartcard-readers-from-eager-rust-agents-with-ld_preload/</guid><category>Linux</category><category>linux</category><category>smartcard</category><category>security</category><category>fedora</category></item><item><title>GeoIP-Aware Firewalling with PF on FreeBSD</title><link>https://hofstede.it/geoip-aware-firewalling-with-pf-on-freebsd/</link><description>&lt;p&gt;Using MaxMind&amp;#8217;s GeoLite2 database with FreeBSD&amp;#8217;s &lt;span class="caps"&gt;PF&lt;/span&gt; firewall to restrict client-facing services to specific countries, reducing brute-force attempts and log noise while keeping essential services globally&amp;nbsp;accessible.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Tue, 13 Jan 2026 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2026-01-13:/geoip-aware-firewalling-with-pf-on-freebsd/</guid><category>FreeBSD</category><category>freebsd</category><category>security</category><category>firewall</category><category>pf</category><category>geoip</category><category>mail</category></item><item><title>Managing FreeBSD Jails with Ansible: The jailexec Connection Plugin</title><link>https://hofstede.it/managing-freebsd-jails-with-ansible-the-jailexec-connection-plugin/</link><description>&lt;p&gt;A custom Ansible connection plugin that enables native management of FreeBSD jails via jexec, without requiring &lt;span class="caps"&gt;SSH&lt;/span&gt; inside each&amp;nbsp;jail.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Wed, 31 Dec 2025 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2025-12-31:/managing-freebsd-jails-with-ansible-the-jailexec-connection-plugin/</guid><category>FreeBSD</category><category>freebsd</category><category>ansible</category><category>jails</category><category>automation</category><category>devops</category></item><item><title>FreeBSD 15 Cloud-Init on Proxmox: Working Around nuageinit’s Network-Config Gap</title><link>https://hofstede.it/freebsd-15-cloud-init-on-proxmox-working-around-nuageinits-network-config-gap/</link><description>&lt;p&gt;Proxmox &lt;span class="caps"&gt;VE&lt;/span&gt; generates network-config v1, but FreeBSD 15&amp;#8217;s nuageinit only speaks v2. Here&amp;#8217;s a script that bridges the gap for static &lt;span class="caps"&gt;IP&lt;/span&gt;&amp;nbsp;configuration.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 28 Dec 2025 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2025-12-28:/freebsd-15-cloud-init-on-proxmox-working-around-nuageinits-network-config-gap/</guid><category>FreeBSD</category><category>freebsd</category><category>proxmox</category><category>cloud-init</category><category>virtualization</category><category>automation</category></item><item><title>Interactive System Troubleshooting with AI: The Linux MCP Server</title><link>https://hofstede.it/interactive-system-troubleshooting-with-ai-the-linux-mcp-server/</link><description>&lt;p&gt;How the linux-mcp-server bridges &lt;span class="caps"&gt;AI&lt;/span&gt; assistants and Linux systems for interactive diagnostics, enabling natural language troubleshooting and system&amp;nbsp;analysis.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Thu, 25 Dec 2025 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2025-12-25:/interactive-system-troubleshooting-with-ai-the-linux-mcp-server/</guid><category>Linux</category><category>linux</category><category>ai</category><category>mcp</category><category>troubleshooting</category><category>fedora</category><category>rhel</category><category>claude</category></item><item><title>Running a Factorio Headless Server on FreeBSD with the Linuxulator</title><link>https://hofstede.it/running-a-factorio-headless-server-on-freebsd-with-the-linuxulator/</link><description>&lt;p&gt;How to run a Factorio dedicated server inside a FreeBSD jail using Linux binary compatibility, with no native port&amp;nbsp;required.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sat, 20 Dec 2025 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2025-12-20:/running-a-factorio-headless-server-on-freebsd-with-the-linuxulator/</guid><category>FreeBSD</category><category>freebsd</category><category>gaming</category><category>jails</category><category>bastille</category><category>factorio</category></item><item><title>Hosting a Static Blog on FreeBSD with Bastille Jails and Automated Deployment</title><link>https://hofstede.it/hosting-a-static-blog-on-freebsd-with-bastille-jails-and-automated-deployment/</link><description>&lt;p&gt;A full-stack overview of hosting a Pelican blog on FreeBSD 15.0 using Bastille jails, Caddy reverse proxy, and automated &lt;span class="caps"&gt;CI&lt;/span&gt;/&lt;span class="caps"&gt;CD&lt;/span&gt; deployment via Forgejo&amp;nbsp;Actions.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 14 Dec 2025 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2025-12-14:/hosting-a-static-blog-on-freebsd-with-bastille-jails-and-automated-deployment/</guid><category>FreeBSD</category><category>freebsd</category><category>jails</category><category>deployment</category><category>caddy</category><category>ci-cd</category><category>bastille</category><category>nginx</category><category>infrastructure</category></item><item><title>Migrating burningboard.net Mastodon instance to a Multi-Jail FreeBSD Setup</title><link>https://hofstede.it/migrating-burningboardnet-mastodon-instance-to-a-multi-jail-freebsd-setup/</link><description>&lt;p&gt;Migrating a Mastodon instance to FreeBSD with BastilleBSD - a multi-jail architecture with aggressive service separation, centralized &lt;span class="caps"&gt;PF&lt;/span&gt; firewalling, and a fully dual-stack network&amp;nbsp;design.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 07 Dec 2025 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2025-12-07:/migrating-burningboardnet-mastodon-instance-to-a-multi-jail-freebsd-setup/</guid><category>FreeBSD</category><category>freebsd</category><category>networking</category><category>mastodon</category><category>ipv6</category></item><item><title>Production-Grade Container Deployment with Podman Quadlets</title><link>https://hofstede.it/production-grade-container-deployment-with-podman-quadlets/</link><description>&lt;p&gt;A Practical Guide to build secure, maintainable multi-container applications with&amp;nbsp;Podman&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 16 Nov 2025 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2025-11-16:/production-grade-container-deployment-with-podman-quadlets/</guid><category>Linux</category><category>linux</category><category>rhel</category><category>podman</category><category>containers</category><category>forgejo</category></item><item><title>FreeBSD Dual-Stack Jails on Hetzner Cloud</title><link>https://hofstede.it/freebsd-dual-stack-jails-on-hetzner-cloud/</link><description>&lt;p&gt;A reproducible dual-stack configuration for FreeBSD on Hetzner Cloud with &lt;span class="caps"&gt;VNET&lt;/span&gt; jails, &lt;span class="caps"&gt;PF&lt;/span&gt; &lt;span class="caps"&gt;NAT&lt;/span&gt; for IPv4, and a /65 split trick to give jails native globally-routable IPv6 from a single&amp;nbsp;/64.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Wed, 12 Nov 2025 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2025-11-12:/freebsd-dual-stack-jails-on-hetzner-cloud/</guid><category>FreeBSD</category><category>freebsd</category><category>networking</category></item><item><title>FreeBSD 15.0 on the ThinkPad T480 — Efficient, Stable, and 8 Hours on Battery</title><link>https://hofstede.it/freebsd-150-on-the-thinkpad-t480-efficient-stable-and-8-hours-on-battery/</link><description>&lt;p&gt;Achieving near-Linux battery life on the T480 while staying purely &lt;span class="caps"&gt;BSD&lt;/span&gt;.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Sun, 09 Nov 2025 00:00:00 +0100</pubDate><guid>tag:blog.hofstede.it,2025-11-09:/freebsd-150-on-the-thinkpad-t480-efficient-stable-and-8-hours-on-battery/</guid><category>FreeBSD</category><category>freebsd</category><category>thinkpad</category><category>power</category><category>xfce</category><category>zfs</category></item><item><title>Simple Temperature Monitoring on FreeBSD</title><link>https://hofstede.it/simple-temperature-monitoring-on-freebsd/</link><description>&lt;p&gt;Using sysctl, coretemp, and shell scripting to monitor &lt;span class="caps"&gt;CPU&lt;/span&gt; and disk temperatures on FreeBSD - a lightweight approach without heavy monitoring&amp;nbsp;frameworks.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Thu, 09 Oct 2025 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2025-10-09:/simple-temperature-monitoring-on-freebsd/</guid><category>FreeBSD</category><category>freebsd</category><category>sysadmin</category></item><item><title>FreeBSD Cheat Sheet for Linux Admins</title><link>https://hofstede.it/freebsd-cheat-sheet-for-linux-admins/</link><description>&lt;p&gt;A side-by-side reference of FreeBSD and Linux commands covering hardware, disks, networking, packages, services, users, and system management - for Linux admins getting started with&amp;nbsp;FreeBSD.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larvitz</dc:creator><pubDate>Fri, 29 Aug 2025 00:00:00 +0200</pubDate><guid>tag:blog.hofstede.it,2025-08-29:/freebsd-cheat-sheet-for-linux-admins/</guid><category>FreeBSD</category><category>freebsd</category><category>linux</category><category>sysadmin</category></item></channel></rss>