From 2b58c14b4354f40cd45ae9c6f543e72c55ac09cf Mon Sep 17 00:00:00 2001
From: Paul Buetow
Date: Tue, 3 Mar 2026 09:08:55 +0200
Subject: Update content for html
---
gemfeed/2022-02-04-computer-operating-systems-i-use.html | 9 ++++++++-
gemfeed/2026-03-02-rcm-ruby-configuration-management-dsl.html | 4 ++--
gemfeed/atom.xml | 6 +++---
3 files changed, 13 insertions(+), 6 deletions(-)
(limited to 'gemfeed')
diff --git a/gemfeed/2022-02-04-computer-operating-systems-i-use.html b/gemfeed/2022-02-04-computer-operating-systems-i-use.html
index d5f277f1..666658e7 100644
--- a/gemfeed/2022-02-04-computer-operating-systems-i-use.html
+++ b/gemfeed/2022-02-04-computer-operating-systems-i-use.html
@@ -13,7 +13,7 @@
Computer operating systems I use(d)
-Published at 2022-02-04T09:58:22+00:00; Updated at 2022-02-18
+Published at 2022-02-04T09:58:22+00:00, last updated Mon 03 Mar 2026 02:14:00 EET 2026
This is a list of Operating Systems I currently use. This list is in no particular order and also will be updated over time. The very first operating system I used was MS-DOS (mainly for games) and the very first Unix like operating system I used was SuSE Linux 5.3. My first smartphone OS was Symbian on a clunky Sony Ericsson device.
+
+I use GarminOS on my Garmin smartwatches. I previously used it on my Garmin Fenix 6 Pro and currently on my Garmin Fenix 7 Pro. It's an excellent smartwatch OS with comprehensive fitness tracking features, outstanding battery life, and tons of functionality. Despite being proprietary, it's the best option for serious sports and health monitoring.
+
+https://www.garmin.com/
+
motionEyeOS
I usually install an army of RaspberryPi 3's in my house before I travel for a prolonged amount of time. All Pi's are equipped with an camera and have motionEyeOS (Linux based video surveillance system) installed. There's a neat Android app in the F-Droid store which let's me keep an eye on everything. I make the Pi's accessible from the internet via reverse SSH tunnels through one of my frontend servers.
diff --git a/gemfeed/2026-03-02-rcm-ruby-configuration-management-dsl.html b/gemfeed/2026-03-02-rcm-ruby-configuration-management-dsl.html
index b334b34d..ac88d6bb 100644
--- a/gemfeed/2026-03-02-rcm-ruby-configuration-management-dsl.html
+++ b/gemfeed/2026-03-02-rcm-ruby-configuration-management-dsl.html
@@ -48,7 +48,7 @@
Why I built RCM
-I've used (and still use) the usual suspects in configuration management: Puppet, Chef, Ansible, etc. They are powerful, but also come with orchestration layers, agents, inventories, and a lot of moving parts. For my personal machines I wanted something smaller: one Ruby process, one configuration file, a few resource types, and good enough safety features.
+I've used (and still use) the usual suspects in configuration management: Puppet, Ansible, etc. They are powerful, but also come with orchestration layers, agents, inventories, and a lot of moving parts. For my personal machines I wanted something smaller: one Ruby process, one configuration file, a few resource types, and good enough safety features.
I've always been a fan of Ruby's metaprogramming features, and this project let me explore them in a focused, practical way.
@@ -228,7 +228,7 @@ HostCondition.new.hostname.is(:earth)
As of this post I'm tagging and releasing **RCM 0.1.0**. About 99% of the code has been written by me so far, and before AI agents take over more of the boilerplate and wiring work, it felt like a good moment to cut a release and mark this mostly‑human baseline.
-Future changes will very likely involve more automated help (including agents like the one you're reading this in), but 0.1.0 is the snapshot of the original, hand‑crafted version of the tool.
+Future changes will very likely involve more automated help, but 0.1.0 is the snapshot of the original, hand‑crafted version of the tool.
What's next
diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml
index a71609f7..d1d5cca5 100644
--- a/gemfeed/atom.xml
+++ b/gemfeed/atom.xml
@@ -1,6 +1,6 @@
- 2026-03-01T21:53:45+02:00
+ 2026-03-03T09:08:49+02:00foo.zone feedTo be in the .zone!
@@ -55,7 +55,7 @@
Why I built RCM
-I've used (and still use) the usual suspects in configuration management: Puppet, Chef, Ansible, etc. They are powerful, but also come with orchestration layers, agents, inventories, and a lot of moving parts. For my personal machines I wanted something smaller: one Ruby process, one configuration file, a few resource types, and good enough safety features.
+I've used (and still use) the usual suspects in configuration management: Puppet, Ansible, etc. They are powerful, but also come with orchestration layers, agents, inventories, and a lot of moving parts. For my personal machines I wanted something smaller: one Ruby process, one configuration file, a few resource types, and good enough safety features.
I've always been a fan of Ruby's metaprogramming features, and this project let me explore them in a focused, practical way.
@@ -235,7 +235,7 @@ HostCondition.new.hostname.is(:earth)
As of this post I'm tagging and releasing **RCM 0.1.0**. About 99% of the code has been written by me so far, and before AI agents take over more of the boilerplate and wiring work, it felt like a good moment to cut a release and mark this mostly‑human baseline.
-Future changes will very likely involve more automated help (including agents like the one you're reading this in), but 0.1.0 is the snapshot of the original, hand‑crafted version of the tool.
+Future changes will very likely involve more automated help, but 0.1.0 is the snapshot of the original, hand‑crafted version of the tool.