summaryrefslogtreecommitdiff
path: root/gemfeed
diff options
context:
space:
mode:
Diffstat (limited to 'gemfeed')
-rw-r--r--gemfeed/2022-02-04-computer-operating-systems-i-use.html9
-rw-r--r--gemfeed/2026-03-02-rcm-ruby-configuration-management-dsl.html4
-rw-r--r--gemfeed/atom.xml6
3 files changed, 13 insertions, 6 deletions
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 @@
</p>
<h1 style='display: inline' id='computer-operating-systems-i-used'>Computer operating systems I use(d)</h1><br />
<br />
-<span class='quote'>Published at 2022-02-04T09:58:22+00:00; Updated at 2022-02-18</span><br />
+<span class='quote'>Published at 2022-02-04T09:58:22+00:00, last updated Mon 03 Mar 2026 02:14:00 EET 2026</span><br />
<br />
<span>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.</span><br />
<br />
@@ -53,6 +53,7 @@
<li>⇢ <a href='#ios-mobile-proprietary'>iOS (mobile proprietary)</a></li>
<li>⇢ <a href='#other-oses'>Other OSes</a></li>
<li>⇢ ⇢ <a href='#infinytime-smartwatch'>InfinyTime (smartwatch)</a></li>
+<li>⇢ ⇢ <a href='#garminos-smartwatch'>GarminOS (smartwatch)</a></li>
<li>⇢ ⇢ <a href='#motioneyeos'>motionEyeOS</a></li>
<li>⇢ ⇢ <a href='#kobo-os-proprietary'>Kobo OS (proprietary)</a></li>
<li>⇢ ⇢ <a href='#android-tv-proprietary'>Android TV (proprietary)</a></li>
@@ -191,6 +192,12 @@ GNU/kFreeBSD rhea.buetow.org 8.0-RELEASE-p5 FreeBSD 8.0-RELEASE-p5 #2: Sat Nov 2
<a class='textlink' href='https://www.pine64.org/pinetime/'>https://www.pine64.org/pinetime/</a><br />
<a class='textlink' href='https://infinitime.io/'>https://infinitime.io/</a><br />
<br />
+<h3 style='display: inline' id='garminos-smartwatch'>GarminOS (smartwatch)</h3><br />
+<br />
+<span>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&#39;s an excellent smartwatch OS with comprehensive fitness tracking features, outstanding battery life, and tons of functionality. Despite being proprietary, it&#39;s the best option for serious sports and health monitoring.</span><br />
+<br />
+<a class='textlink' href='https://www.garmin.com/'>https://www.garmin.com/</a><br />
+<br />
<h3 style='display: inline' id='motioneyeos'>motionEyeOS</h3><br />
<br />
<span>I usually install an army of RaspberryPi 3&#39;s in my house before I travel for a prolonged amount of time. All Pi&#39;s are equipped with an camera and have motionEyeOS (Linux based video surveillance system) installed. There&#39;s a neat Android app in the F-Droid store which let&#39;s me keep an eye on everything. I make the Pi&#39;s accessible from the internet via reverse SSH tunnels through one of my frontend servers.</span><br />
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 @@
</ul><br />
<h2 style='display: inline' id='why-i-built-rcm'>Why I built RCM</h2><br />
<br />
-<span>I&#39;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.</span><br />
+<span>I&#39;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.</span><br />
<br />
<span>I&#39;ve always been a fan of Ruby&#39;s metaprogramming features, and this project let me explore them in a focused, practical way.</span><br />
<br />
@@ -228,7 +228,7 @@ HostCondition.new.hostname.is(:earth)
<br />
<span>As of this post I&#39;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.</span><br />
<br />
-<span>Future changes will very likely involve more automated help (including agents like the one you&#39;re reading this in), but 0.1.0 is the snapshot of the original, hand‑crafted version of the tool.</span><br />
+<span>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.</span><br />
<br />
<h2 style='display: inline' id='what-s-next'>What&#39;s next</h2><br />
<br />
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 @@
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
- <updated>2026-03-01T21:53:45+02:00</updated>
+ <updated>2026-03-03T09:08:49+02:00</updated>
<title>foo.zone feed</title>
<subtitle>To be in the .zone!</subtitle>
<link href="https://foo.zone/gemfeed/atom.xml" rel="self" />
@@ -55,7 +55,7 @@
</ul><br />
<h2 style='display: inline' id='why-i-built-rcm'>Why I built RCM</h2><br />
<br />
-<span>I&#39;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.</span><br />
+<span>I&#39;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.</span><br />
<br />
<span>I&#39;ve always been a fan of Ruby&#39;s metaprogramming features, and this project let me explore them in a focused, practical way.</span><br />
<br />
@@ -235,7 +235,7 @@ HostCondition.new.hostname.is(:earth)
<br />
<span>As of this post I&#39;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.</span><br />
<br />
-<span>Future changes will very likely involve more automated help (including agents like the one you&#39;re reading this in), but 0.1.0 is the snapshot of the original, hand‑crafted version of the tool.</span><br />
+<span>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.</span><br />
<br />
<h2 style='display: inline' id='what-s-next'>What&#39;s next</h2><br />
<br />