FreeBSD jails are one of the operating system’s most elegant features. Introduced over two decades ago, they provide lightweight, secure isolation for processes and filesystems without the overhead of full virtual machines or the complexity of Linux container setups. What makes them especially appealing today is how straightforward it is to create and destroy them — no bridges, no epair interfaces, no VNET, no NAT rules, no sysctl tweaking, and no permanent rc.conf hacks. In this post, I’ll walk you through the exact process I use to spin up a clean FreeBSD 14.3 jail and then completely remove it, demonstrating just how simple and lightweight the whole thing is.

In the world of open-source operating systems, OpenBSD and FreeBSD are renowned for their stability, security, and excellent audio support. This guide describes a clean, automated setup for streaming high-quality music from a FreeBSD-based NAS to an OpenBSD machine connected to a hi-fi DAC over optical fiber (S/PDIF). The solution uses **Music Player Daemon (MPD)** on the FreeBSD NAS as the music server and **sndio** for low-latency, high-fidelity remote audio output to the OpenBSD client. The setup ensures that turning on the amplifier and DAC automatically prepares the OpenBSD audio system and starts playback on the NAS — all without manual intervention.

Tired of your WiFi vanishing mid call, leaving you staring at a spinning wheel of movie? I've been there—furious, fumbling for my phone's hotspot like it's 2015. But no more. I just wired up a sneaky 4G sidekick: the TP-Link MR600. It's like a ninja router—silent, speedy, and ready to swoop in when your ISP flakes out. One ping fails? Boom. Traffic flips to cellular backup in seconds. No drama, no downtime. All powered by some clever OpenBSD magic that makes it feel effortless.

There are tones of zsh config on internet, but none were matching my needs. Thus, I've decided to build mine and to share it with you. Feel free to copy / re-use part of it.

Every year stand one of the biggest OpenSource conference, and this is close to my house. The subject of this blog is to explain how I've configured my OpenBSD 7.6 and FreeBSD 14.1 to connect to their wifi which only "speak" IPv6 This is not a setup I encountered frequently, and I just want to remember how I did it ;)

This is a very spimple idea which avoid that cron job sends too much emails. This script store the hash of the email and, based on that, decide that this is relevant or not.

In this blog I'll share a one line command awk allowing me to see only new lines since previous check. I'm heavily using this feature in my daily scripts: /etc/daily.local or /etc/weekly.local. This allows me to only see what has changed since previous days. This is really useful for [last](https://man.openbsd.org/last) command, for [dmesg](https://man.openbsd.org/dmesg) or for `/var/logmessages`.

When managing a cluster of OpenBSD machines, keeping configuration files synchronized between nodes is essential for maintaining high availability and consistency. One effective approach for automating this process is to use `entr`, a simple and powerful utility for executing arbitrary commands when files change.

In this blog, I explain how to setup high availability services between 2 different machines thanks to carp.

I was frustrated that recurrent jobs are not running like I want via the [cron](https://man.openbsd.org/cron) on my laptops. I was looking for something which trigger actions every hours the machine is running, or once every day, or once every week. For a daily task, it doesn't matter if we are the morning or the evening. For a weekly task doesn't matter if we are saturday, sunday or monday. So I wrote a quite simple shell script dealing with this job, I've called it "vdcron" **Note of 2024/11/10**: This post has few days, and I receive questions about "why not anacron?". So, I've just completed this post with this aspect.