From 5940d99b099abb1745660e21bd16387922a0e69a Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 11 Jan 2026 10:48:19 +0200 Subject: Update content for html --- about/resources.html | 206 ++++++++++----------- ...4-12-03-f3s-kubernetes-with-freebsd-part-2.html | 76 ++++++-- gemfeed/atom.xml | 78 ++++++-- index.html | 2 +- uptime-stats.html | 2 +- 5 files changed, 232 insertions(+), 132 deletions(-) diff --git a/about/resources.html b/about/resources.html index 66f68843..2cff1495 100644 --- a/about/resources.html +++ b/about/resources.html @@ -50,54 +50,54 @@ In random order:


Technical references



@@ -106,10 +106,10 @@
@@ -118,44 +118,44 @@ In random order:


Here are notes of mine for some of the books

@@ -164,31 +164,31 @@ Some of these were in-person with exams; others were online learning lectures only. In random order:


Technical guides



These are not whole books, but guides (smaller or larger) which I found very useful. in random order:


Podcasts



@@ -197,21 +197,21 @@ In random order:


Podcasts I liked



@@ -219,10 +219,10 @@

Newsletters I like


@@ -230,28 +230,28 @@ This is a mix of tech and non-tech newsletters I am subscribed to. In random order:


Magazines I like(d)



This is a mix of tech I like(d). I may not be a current subscriber, but now and then, I buy an issue. In random order:


Formal education



diff --git a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.html b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.html index 80ba4748..32e73b23 100644 --- a/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.html +++ b/gemfeed/2024-12-03-f3s-kubernetes-with-freebsd-part-2.html @@ -59,8 +59,9 @@
  • ⇢ CPU throttling
  • Wake-on-LAN Setup
  • ⇢ Setting up WoL on the laptop
    • -
  • ⇢ Testing WoL
    • +
  • ⇢ Testing WoL and Shutdown
  • ⇢ WoL from WiFi
    • +
  • ⇢ Remote Shutdown via SSH
  • ⇢ BIOS Configuration
  • Conclusion

    • @@ -371,20 +372,28 @@ http://www.gnu.org/software/src-highlite --> 
    [paul@earth]~% sudo dnf install -y wol

    -Next, I created a simple script (~/bin/wol-f3s) to wake the machines:
    +Next, I created a simple script (~/bin/wol-f3s) to wake and shutdown the machines:

    #!/bin/bash
-# Wake-on-LAN script for f3s cluster (f0, f1, f2)
+# Wake-on-LAN and shutdown script for f3s cluster (f0, f1, f2)
 
 # MAC addresses
 F0_MAC="e8:ff:1e:d7:1c:ac"  # f0 (192.168.1.130)
 F1_MAC="e8:ff:1e:d7:1e:44"  # f1 (192.168.1.131)
 F2_MAC="e8:ff:1e:d7:1c:a0"  # f2 (192.168.1.132)
 
+# IP addresses
+F0_IP="192.168.1.130"
+F1_IP="192.168.1.131"
+F2_IP="192.168.1.132"
+
+# SSH user
+SSH_USER="paul"
+
 # Broadcast address for your LAN
 BROADCAST="192.168.1.255"
 
@@ -395,7 +404,18 @@ wake() {
     wol -i "$BROADCAST" "$mac"
 }
 
-case "${1:-all}" in
+shutdown_host() {
+    local name=$1
+    local ip=$2
+    echo "Shutting down $name ($ip)..."
+    ssh -o ConnectTimeout=5 "$SSH_USER@$ip" "doas poweroff" 2>/dev/null && \
+        echo "  ✓ Shutdown command sent to $name" || \
+        echo "  ✗ Failed to reach $name (already down?)"
+}
+
+ACTION="${1:-all}"
+
+case "$ACTION" in
     f0) wake "f0" "$F0_MAC" ;;
     f1) wake "f1" "$F1_MAC" ;;
     f2) wake "f2" "$F2_MAC" ;;
@@ -404,8 +424,16 @@ wake() {
         wake "f1" "$F1_MAC"
         wake "f2" "$F2_MAC"
         ;;
+    shutdown|poweroff|down)
+        shutdown_host "f0" "$F0_IP"
+        shutdown_host "f1" "$F1_IP"
+        shutdown_host "f2" "$F2_IP"
+        echo ""
+        echo "✓ Shutdown commands sent to all machines."
+        exit 0
+        ;;
     *)
-        echo "Usage: $0 [f0|f1|f2|all]"
+        echo "Usage: $0 [f0|f1|f2|all|shutdown]"
         exit 1
         ;;
 esac
@@ -414,27 +442,34 @@ echo ""
 echo "✓ WoL packets sent. Machines should boot in a few seconds."

    -After making the script executable with chmod +x ~/bin/wol-f3s, I can now wake the machines with simple commands:
    +After making the script executable with chmod +x ~/bin/wol-f3s, I can now control the machines with simple commands:

    -
    [paul@earth]~% wol-f3s        # Wake all three
-[paul@earth]~% wol-f3s f0     # Wake only f0
+
    [paul@earth]~% wol-f3s          # Wake all three
+[paul@earth]~% wol-f3s f0       # Wake only f0
+[paul@earth]~% wol-f3s shutdown # Shutdown all three via SSH
 
    
 
    
-
    Testing WoL

    
+
    Testing WoL and Shutdown

    
 
    
-To test the setup, I shutdown all three machines:
    
+To test the setup, I shutdown all three machines using the script's shutdown function:
    
 
    
 
-
    [paul@earth]~% ssh paul@192.168.1.130 "doas poweroff"
-[paul@earth]~% ssh paul@192.168.1.131 "doas poweroff"
-[paul@earth]~% ssh paul@192.168.1.132 "doas poweroff"
+
    [paul@earth]~% wol-f3s shutdown
+Shutting down f0 (192.168.1.130)...
+  ✓ Shutdown command sent to f0
+Shutting down f1 (192.168.1.131)...
+  ✓ Shutdown command sent to f1
+Shutting down f2 (192.168.1.132)...
+  ✓ Shutdown command sent to f2
+
+✓ Shutdown commands sent to all machines.
 
    
 
    
 After waiting for them to fully power down (about 1 minute), I sent the WoL magic packets:
    
@@ -462,6 +497,21 @@ Waking up e8:ff:1e:d7:1c:a0...
 
    
 This makes WoL very convenient - I can wake the cluster from anywhere in my home, whether I'm on WiFi or ethernet.
    
 
    
+
    Remote Shutdown via SSH

    
+
    
+While Wake-on-LAN handles powering on the machines remotely, I also added a shutdown function to the script for convenience. The wol-f3s shutdown command uses SSH to connect to each machine and execute doas poweroff, gracefully shutting them all down.
    
+
    
+This is particularly useful for power saving - when I'm done working with the cluster for the day, I can simply run:
    
+
    
+
+
    [paul@earth]~% wol-f3s shutdown
+
    
+
    
+And all three machines will shut down cleanly. The next time I need them, a simple wol-f3s command wakes them all back up. This combination makes the cluster very energy-efficient while maintaining quick access when needed.
    
+
    
 
    BIOS Configuration

    
 
    
 For WoL to work reliably, make sure to check the BIOS settings on each Beelink:
    
diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml
index da1b65c7..d9eda66d 100644
--- a/gemfeed/atom.xml
+++ b/gemfeed/atom.xml
@@ -1,6 +1,6 @@
 
 
-    2026-01-11T10:37:38+02:00
+    2026-01-11T10:46:34+02:00
     foo.zone feed
     To be in the .zone!
     
@@ -13637,8 +13637,9 @@ Jan 26 17:36:32 f2 apcupsd[2159]: apcupsd shutdown succeeded
 
  • ⇢ CPU throttling
    • 
 
  • Wake-on-LAN Setup
    • 
 
  • ⇢ Setting up WoL on the laptop
    • 
-
  • ⇢ Testing WoL
    • 
+
  • ⇢ Testing WoL and Shutdown
    • 
 
  • ⇢ WoL from WiFi
    • 
+
  • ⇢ Remote Shutdown via SSH
    • 
 
  • ⇢ BIOS Configuration
    • 
 
  • Conclusion
    • 
 
    
@@ -13949,20 +13950,28 @@ http://www.gnu.org/software/src-highlite -->
 
    [paul@earth]~% sudo dnf install -y wol
 
    
 
    
-Next, I created a simple script (~/bin/wol-f3s) to wake the machines:
    
+Next, I created a simple script (~/bin/wol-f3s) to wake and shutdown the machines:
    
 
    
 
 
    #!/bin/bash
-# Wake-on-LAN script for f3s cluster (f0, f1, f2)
+# Wake-on-LAN and shutdown script for f3s cluster (f0, f1, f2)
 
 # MAC addresses
 F0_MAC="e8:ff:1e:d7:1c:ac"  # f0 (192.168.1.130)
 F1_MAC="e8:ff:1e:d7:1e:44"  # f1 (192.168.1.131)
 F2_MAC="e8:ff:1e:d7:1c:a0"  # f2 (192.168.1.132)
 
+# IP addresses
+F0_IP="192.168.1.130"
+F1_IP="192.168.1.131"
+F2_IP="192.168.1.132"
+
+# SSH user
+SSH_USER="paul"
+
 # Broadcast address for your LAN
 BROADCAST="192.168.1.255"
 
@@ -13973,7 +13982,18 @@ wake() {
     wol -i "$BROADCAST" "$mac"
 }
 
-case "${1:-all}" in
+shutdown_host() {
+    local name=$1
+    local ip=$2
+    echo "Shutting down $name ($ip)..."
+    ssh -o ConnectTimeout=5 "$SSH_USER@$ip" "doas poweroff" 2>/dev/null && \
+        echo "  ✓ Shutdown command sent to $name" || \
+        echo "  ✗ Failed to reach $name (already down?)"
+}
+
+ACTION="${1:-all}"
+
+case "$ACTION" in
     f0) wake "f0" "$F0_MAC" ;;
     f1) wake "f1" "$F1_MAC" ;;
     f2) wake "f2" "$F2_MAC" ;;
@@ -13982,8 +14002,16 @@ wake() {
         wake "f1" "$F1_MAC"
         wake "f2" "$F2_MAC"
         ;;
+    shutdown|poweroff|down)
+        shutdown_host "f0" "$F0_IP"
+        shutdown_host "f1" "$F1_IP"
+        shutdown_host "f2" "$F2_IP"
+        echo ""
+        echo "✓ Shutdown commands sent to all machines."
+        exit 0
+        ;;
     *)
-        echo "Usage: $0 [f0|f1|f2|all]"
+        echo "Usage: $0 [f0|f1|f2|all|shutdown]"
         exit 1
         ;;
 esac
@@ -13992,27 +14020,34 @@ echo ""
 echo "✓ WoL packets sent. Machines should boot in a few seconds."
 
    
 
    
-After making the script executable with chmod +x ~/bin/wol-f3s, I can now wake the machines with simple commands:
    
+After making the script executable with chmod +x ~/bin/wol-f3s, I can now control the machines with simple commands:
    
 
    
 
-
    [paul@earth]~% wol-f3s        # Wake all three
-[paul@earth]~% wol-f3s f0     # Wake only f0
+
    [paul@earth]~% wol-f3s          # Wake all three
+[paul@earth]~% wol-f3s f0       # Wake only f0
+[paul@earth]~% wol-f3s shutdown # Shutdown all three via SSH
 
    
 
    
-
    Testing WoL

    
+
    Testing WoL and Shutdown

    
 
    
-To test the setup, I shutdown all three machines:
    
+To test the setup, I shutdown all three machines using the script's shutdown function:
    
 
    
 
-
    [paul@earth]~% ssh paul@192.168.1.130 "doas poweroff"
-[paul@earth]~% ssh paul@192.168.1.131 "doas poweroff"
-[paul@earth]~% ssh paul@192.168.1.132 "doas poweroff"
+
    [paul@earth]~% wol-f3s shutdown
+Shutting down f0 (192.168.1.130)...
+  ✓ Shutdown command sent to f0
+Shutting down f1 (192.168.1.131)...
+  ✓ Shutdown command sent to f1
+Shutting down f2 (192.168.1.132)...
+  ✓ Shutdown command sent to f2
+
+✓ Shutdown commands sent to all machines.
 
    
 
    
 After waiting for them to fully power down (about 1 minute), I sent the WoL magic packets:
    
@@ -14040,6 +14075,21 @@ Waking up e8:ff:1e:d7:1c:a0...
 
    
 This makes WoL very convenient - I can wake the cluster from anywhere in my home, whether I'm on WiFi or ethernet.
    
 
    
+
    Remote Shutdown via SSH

    
+
    
+While Wake-on-LAN handles powering on the machines remotely, I also added a shutdown function to the script for convenience. The wol-f3s shutdown command uses SSH to connect to each machine and execute doas poweroff, gracefully shutting them all down.
    
+
    
+This is particularly useful for power saving - when I'm done working with the cluster for the day, I can simply run:
    
+
    
+
+
    [paul@earth]~% wol-f3s shutdown
+
    
+
    
+And all three machines will shut down cleanly. The next time I need them, a simple wol-f3s command wakes them all back up. This combination makes the cluster very energy-efficient while maintaining quick access when needed.
    
+
    
 
    BIOS Configuration

    
 
    
 For WoL to work reliably, make sure to check the BIOS settings on each Beelink:
    
diff --git a/index.html b/index.html
index 7cc74f4c..1b0f84ef 100644
--- a/index.html
+++ b/index.html
@@ -13,7 +13,7 @@
 
    
 
    Hello!

    
 
    
-This site was generated at 2026-01-11T10:37:38+02:00 by Gemtexter
    
+This site was generated at 2026-01-11T10:46:34+02:00 by Gemtexter
    
 
    
 Welcome to the foo.zone!
    
 
    
diff --git a/uptime-stats.html b/uptime-stats.html
index a1d5586a..ef4181c0 100644
--- a/uptime-stats.html
+++ b/uptime-stats.html
@@ -13,7 +13,7 @@
 
    
 
    My machine uptime stats

    
 
    
-This site was last updated at 2026-01-11T10:37:38+02:00
    
+This site was last updated at 2026-01-11T10:46:34+02:00
    
 
    
 The following stats were collected via uptimed on all of my personal computers over many years and the output was generated by guprecords, the global uptime records stats analyser of mine.
    
 
    
-- 
cgit v1.2.3