<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Raspberry Pi on steeman.be</title><link>https://www.steeman.be/categories/raspberry-pi/</link><description>Recent content in Raspberry Pi on steeman.be</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 25 Mar 2026 12:00:00 +0100</lastBuildDate><atom:link href="https://www.steeman.be/categories/raspberry-pi/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a Robust Linux Backup Strategy with Borg</title><link>https://www.steeman.be/posts/building-a-robust-linux-backup-strategy-with-borg/</link><pubDate>Wed, 25 Mar 2026 12:00:00 +0100</pubDate><guid>https://www.steeman.be/posts/building-a-robust-linux-backup-strategy-with-borg/</guid><description>&lt;p&gt;We have all heard the mantra: backups are important, test your backups, follow the 3-2-1 rule. But actually implementing a backup strategy that works reliably, alerts you when something goes wrong, and survives reboots is another matter entirely. This is the story of how I built — and continue to evolve — a comprehensive backup system for my homelab server.&lt;/p&gt;

&lt;h2 class="relative group"&gt;Why I finally got serious about backups
 &lt;div id="why-i-finally-got-serious-about-backups" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#why-i-finally-got-serious-about-backups" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;The catalyst was a failing hard drive. My backup disk, a WD Elements 4.5TB USB HDD, started showing signs of age. It had been quietly handling daily backups for years, but I could see the writing on the wall. This was the wake-up call I needed to not just replace the disk, but to rethink the entire backup strategy.&lt;/p&gt;</description></item><item><title>Raspberry Pi door bell</title><link>https://www.steeman.be/posts/raspberry-pi-door-bell/</link><pubDate>Fri, 20 Mar 2015 00:00:00 +0000</pubDate><guid>https://www.steeman.be/posts/raspberry-pi-door-bell/</guid><description>&lt;p&gt;I’ve always wanted a door bell that could e-mail me a picture whenever someone came to my door. This should be fairly easy using a Raspberry Pi, so I built one. Here’s the build log and code if you would like to build one yourself.&lt;/p&gt;

&lt;h2 class="relative group"&gt;Raspberry Pi
 &lt;div id="raspberry-pi" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#raspberry-pi" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;The core of this door bell is a Raspberry Pi, a small form factor and cheap computer board. I’m using the Raspi Model B+, although nowadays a newer and improved Model 2 is available. &lt;a href="https://www.steeman.be/images/Raspberry%20Pi%20door%20bell/raspi.jpg" target="_blank" rel="noopener"&gt;&lt;figure&gt;&lt;img
 class="my-0 rounded-md"
 loading="lazy"
 decoding="async"
 fetchpriority="low"
 alt=""
 src="https://www.steeman.be/images/Raspberry%20Pi%20door%20bell/raspi%20thumb.jpg"
 &gt;&lt;/figure&gt;
&lt;/a&gt;
&lt;/p&gt;</description></item><item><title>Installing VSCP on a Raspberry Pi</title><link>https://www.steeman.be/posts/installing-vscp-on-a-raspberry-pi/</link><pubDate>Wed, 04 Mar 2015 00:00:00 +0000</pubDate><guid>https://www.steeman.be/posts/installing-vscp-on-a-raspberry-pi/</guid><description>&lt;p&gt;Here’s an overview of how to install &lt;em&gt;vscp_software&lt;/em&gt; on a Raspberry Pi. It is based on &lt;a href="http://www.vscp.org/docs/vscpd/doku.php?id=setting_up_the_system_on_unix"&gt;the tutorial on setting up the VSCP daemon on Unix&lt;/a&gt;
. I’m not only giving the commands but also the verbose output for most commands, so grease up your scroll wheel :-)&lt;/p&gt;

&lt;h2 class="relative group"&gt;Updating the system
 &lt;div id="updating-the-system" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#updating-the-system" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;First we need to make sure all installed packages on our system are up-to-date. We’ll do this by issuing &lt;em&gt;sudo apt-get update&lt;/em&gt; to update the package list and status, and &lt;em&gt;sudo apt-get upgrade&lt;/em&gt; to upgrade those which have newer versions.&lt;/p&gt;</description></item><item><title>Raspberry Pi setup</title><link>https://www.steeman.be/posts/raspberry-pi-setup/</link><pubDate>Tue, 03 Mar 2015 00:00:00 +0000</pubDate><guid>https://www.steeman.be/posts/raspberry-pi-setup/</guid><description>&lt;p&gt;This post documents how I have set up my Raspberry Pi (model B+) for double duty as a VSCP daemon server and a pimped doorbell. This page is mostly for my own reference.&lt;/p&gt;

&lt;h2 class="relative group"&gt;Static IP
 &lt;div id="static-ip" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#static-ip" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;Find the DHCP address assigned to the Raspi. Log onto the Raspi through SSH and note the current IP settings:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;sudo ifconfig
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Then edit the &lt;em&gt;/etc/network/interfaces&lt;/em&gt; file.&lt;/p&gt;</description></item></channel></rss>