<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" >
<channel>
  <title>Vincent's blog</title>
  <link>https://vincentdelft.be/rss</link>
  <description>Vincent's ideas</description>
  <atom:link href="https://vincentdelft.be/rss" rel="self" type="application/rss+xml" />
  <lastBuildDate>Sun, 04 Oct 2026 17:26:00 +0100</lastBuildDate>
  
   <item>
      <pubDate>Sun, 04 Oct 2026 17:26:00 +0100</pubDate>
      <link>https://vincentdelft.be/post/post_20261004</link> 
      <guid>https://vincentdelft.be/post/post_20261004</guid> 
      <title>Recreating OpenBSD's daily and weekly reports on Void Linux with ZFS: the checks I run and why</title>
      <description><![CDATA[<p><img alt="Give a shoutout to  Max Payload on unsplash.com" src="/static/post/post_20261004/bench.jpg" title="Give a shoutout to  Max Payload on unsplash.com" />
On OpenBSD, /etc/daily and /etc/weekly quietly watch over the machine and mail you a report. On FreeBSD, periodic(8) does the same. I love that model, but when I wanted ZFS on my laptop, Void Linux turned out to have better drivers than FreeBSD for my hardware. The catch is that Void ships no periodic maintenance at all. So I wrote two small POSIX shell scripts, one daily and one weekly, that mimic the BSD reports and add checks specific to ZFS and to a laptop. They log everything, compare today with yesterday, and interrupt me only for real problems such as a degraded pool, a failing disk, or a kernel installed without its ZFS module. This post walks through each check, the command behind it, and why it is there.</p>
<p>I can put both at the top of void-zfs-maintenance-blog.md if you want. I can also write a shorter, punchier title, for example "Daily and weekly maintenance on Void Linux with ZFS, the BSD way", which matches the current heading of the post.</p>]]></description>
   </item>
   
   <item>
      <pubDate>Thu, 24 Sep 2026 21:22:00 +0100</pubDate>
      <link>https://vincentdelft.be/post/post_20260924</link> 
      <guid>https://vincentdelft.be/post/post_20260924</guid> 
      <title>A proposition of Boot Environment for VoidLinux running on ZFS</title>
      <description><![CDATA[<p><img alt="Give a shoutout to Irham Setyaki on unsplash.com" src="/static/post/post_20260924/start.jpg" title="Give a shoutout to Irham Setyaki on unsplash.com" />
If you run FreeBSD on ZFS, you probably can't imagine upgrading without
<code>bectl</code> anymore. Take a boot environment, run <code>freebsd-update</code> or <code>pkg upgrade</code>,
and if something goes wrong, reboot into the previous state. No backup to
restore, no rescue USB stick.</p>]]></description>
   </item>
   
   <item>
      <pubDate>Fri, 18 Sep 2026 22:47:00 +0100</pubDate>
      <link>https://vincentdelft.be/post/post_20260918</link> 
      <guid>https://vincentdelft.be/post/post_20260918</guid> 
      <title>Void Linux is very dangerous for FreeBSD on my laptop</title>
      <description><![CDATA[<p><img alt="Give a shoutout to aa aa on unsplash.com" src="https://vincentdelft.be/static/post/post_20260918/void.jpg" title="Give a shoutout to aa aa on unsplash.com" />
This whole thing started because of <a href="https://it-notes.dragas.net/2025/12/22/void-linux-zfs-hibernation-guide/">Stefano and his blog</a>. His guide to installing Void Linux on an encrypted ZFS root with hibernation support was the thing that got me curious enough to actually try it — and, as these things go, curiosity turned into an afternoon spent repartitioning a laptop I use every day. My setup below is simpler than his (no LUKS-encrypted swap, no hibernation), because I just wanted ZFS-on-root dual-booted alongside my existing FreeBSD/GhostBSD/OpenBSD rEFInd menu, but the bones of the approach — and the credit for pointing me at zfsbootmenu in the first place — are his.</p>]]></description>
   </item>
   
  </channel>
</rss>