From b816e41ee40921d6c61964a850edceb0427bd0f2 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 22 Jun 2025 18:58:43 +0300 Subject: Update content for html --- about/resources.html | 194 ++++++------ gemfeed/2025-07-22-task-samurai.html | 141 +++++++++ gemfeed/DRAFT-distributed-systems-simulator.html | 320 +++++++++++++++++++ .../DRAFT-f3s-kubernetes-with-freebsd-part-6.html | 176 ++++++----- gemfeed/atom.xml | 346 +++++++++------------ gemfeed/index.html | 1 + gemfeed/task-samurai/logo.png | Bin 0 -> 161388 bytes gemfeed/task-samurai/screenshot.png | Bin 0 -> 194648 bytes index.html | 3 +- uptime-stats.html | 60 ++-- 10 files changed, 842 insertions(+), 399 deletions(-) create mode 100644 gemfeed/2025-07-22-task-samurai.html create mode 100644 gemfeed/DRAFT-distributed-systems-simulator.html create mode 100644 gemfeed/task-samurai/logo.png create mode 100644 gemfeed/task-samurai/screenshot.png diff --git a/about/resources.html b/about/resources.html index 988723e7..359669ca 100644 --- a/about/resources.html +++ b/about/resources.html @@ -50,107 +50,107 @@ In random order:


Technical references



I didn't read them from the beginning to the end, but I am using them to look up things. The books are in random order:


Self-development and soft-skills books



In random order:


Here are notes of mine for some of the books

@@ -159,30 +159,30 @@ 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


@@ -192,48 +192,48 @@ In random order:


Podcasts I liked



I liked them but am not listening to them anymore. The podcasts have either "finished" (no more episodes) or I stopped listening to them due to time constraints or a shift in my interests.


Newsletters I like



This is a mix of tech and non-tech newsletters I am subscribed to. In random order:


Magazines I like(d)


@@ -241,10 +241,10 @@ 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/2025-07-22-task-samurai.html b/gemfeed/2025-07-22-task-samurai.html new file mode 100644 index 00000000..8ea20ccb --- /dev/null +++ b/gemfeed/2025-07-22-task-samurai.html @@ -0,0 +1,141 @@ + + + + +Task Samurai + + + + + +

+Home | Markdown | Gemini +

+

Task Samurai


+
+Published at 2025-06-22T18:49:11+03:00
+
+Task Samurai Logo
+
+

Table of Contents


+
+
+

Introduction


+
+Task Samurai is a fast terminal interface for Taskwarrior written in Go using the Bubble Tea framework. It displays your tasks in a table and allows you to manage them without leaving your keyboard.
+
+https://taskwarrior.org
+https://github.com/charmbracelet/bubbletea
+
+

Why does this exist?


+
+
+Given the current industry trend and the rapid advancements in technology, it has become clear that experimenting with AI-assisted coding tools is almost a necessity to stay relevant. Embracing these new developments doesn't mean abandoning traditional coding; instead, it means integrating new capabilities into your workflow to stay ahead in a fast-evolving field.
+
+

How it works


+
+Task Samurai invokes the task command to read and modify tasks. The tasks are displayed in a Bubble Tea table, where each row represents a task. Hotkeys trigger Taskwarrior commands such as starting, completing or annotating tasks. The UI refreshes automatically after each action, so the table is always up to date.
+
+Task Samurai Screenshot
+
+

Lessons Learned from Building Task Samurai with Agentic Coding


+
+If you've ever wanted to supercharge your dev speed—or just throw a fireworks display in your terminal—here's a peek behind the scenes of building Task Samurai. This terminal interface for Taskwarrior was developed entirely through agentic coding by me, leveraging OpenAI Codex to do all the heavy lifting (and sometimes some cleanup afterwards). The project name might be snappy, but it was the iterative, semi-automated workflow that made the impact.
+
+As a side note, I was trying out OpenAI Codex because I regularly run out of Claude Code CLI (another agentic coding tool I am trying out currently) credits (it still happens!), but Codex was still available to me. So, I seized the opportunity to push agentic coding a bit more.
+
+

How It Went Down


+
+Task Samurai's codebase came together quickly: the entire Git history spans from June 19 to 22, 2025, culminating in 179 commits. Here are the broad strokes:
+
+
+Most big breakthroughs (and bug introductions) came during that middle day of intense iteration. The latter stages were all about smoothing out the rough edges.
+
+

What Went Wrong


+
+Going agentic isn't all smooth sailing. Here are the hiccups I ran into, plus a few hard-earned lessons:
+
+
+

Patterns That Helped


+
+Despite the chaos, a few strategies kept things moving:
+
+
+

What I Learned Using Agentic Coding


+
+Stepping into agentic coding with Codex as my "pair programmer" was a genuine shift. I learned a ton—not just about automating code generation, but also about how you have to tightly steer, guide, and audit every line as things move at breakneck speed. I must admit, I sometimes lost track of what all the generated code was actually doing. But as the features seemed to work after a few iterations, I was satisfied.
+
+Discussing requirements with Codex forced me to clarify features and spot logical pitfalls earlier. All those fast iterations meant I was constantly coaxing more helpful, less ambiguous code out of the model—making me rethink how to break features into clear, testable steps. I now see agentic coding not just as a productivity tool but also as a learning accelerator.
+
+

How Much Time Did I Save?


+
+Here's the million-dollar (or many hours saved) question: Did it buy me speed?
+
+Let's do some back-of-the-envelope math:
+
+
+

Where and how to get it


+
+Go to:
+
+https://codeberg.org/snonux/tasksamurai
+
+And follow the README.md!
+
+

Wrapping Up


+
+Building Task Samurai with agentic coding was a wild ride—rapid feature growth, plenty of churns, countless fast fixes, and more merge commits I'd expected. The big lessons? Keep the iterations short, keep tests and documentation concise, and review and refine for final polish at the end. Even with the bumps along the way, shipping a polished terminal UI in days instead of weeks is a testament to the raw power (and some hazards) of agentic development.
+
+While working on Task Samuray, there were times I genuinely missed manual coding and the satisfaction that comes from writing every line yourself, debugging issues through sheer logic, and crafting solutions from scratch. However, this is the direction in which the industry seems to be shifting, unfortunately. If applied correctly, AI will boost performance, and if you don't use AI, your next performance review may be awkward.
+
+If you're considering going agentic, be prepared for a sprint, keep your toolkit sharp, and be ready to learn a lot along the way.
+
+Personally, I am not sure whether I like where the industry is going with agentic coding. I love "traditional" coding, and with agentic coding you operate at a higher level and don't interact directly with code as often, which I would miss. I think that in the future, designing, reviewing, and being able to read and understand code will be more important than writing code by hand.
+
+Do you have any thoughts on that? I hope, I am partially wrong at least.
+
+E-Mail your comments to paul@nospam.buetow.org :-)
+
+Back to the main site
+

+Generated with Gemtexter 3.0.1-develop | +served by OpenBSD/relayd(8)+httpd(8) | +Site Mirrors +

+ + diff --git a/gemfeed/DRAFT-distributed-systems-simulator.html b/gemfeed/DRAFT-distributed-systems-simulator.html new file mode 100644 index 00000000..d5327355 --- /dev/null +++ b/gemfeed/DRAFT-distributed-systems-simulator.html @@ -0,0 +1,320 @@ + + + + +Distributed Systems Simulator + + + + + +

+Home | Markdown | Gemini +

+

Distributed Systems Simulator


+
+This blog explores the Java-based Distributed Simulator program I've created specifically for simulating distributed systems protocols, offering both built-in implementations of common algorithms and an extensible framework that allows researchers and practitioners to implement and test their own custom protocols within the simulation environment.
+
+

Table of Contents


+
+
+

Motivation


+
+Distributed systems are notoriously complex, with intricate interactions between multiple nodes, network partitions, and failure scenarios that can be difficult to understand and debug in production environments. A distributed systems simulator provides an invaluable learning tool that allows developers and students to experiment with different architectures, observe how systems behave under various failure conditions, and gain hands-on experience with concepts like consensus algorithms, replication strategies, and fault tolerance—all within a controlled, repeatable environment. By abstracting away the operational overhead of managing real distributed infrastructure, simulators enable focused exploration of system design principles and help bridge the gap between theoretical knowledge and practical understanding of how distributed systems actually work in the real world.
+
+In the literature, one can find many different definitions of a distributed system. Many of these definitions differ from each other, making it difficult to find a single definition that stands alone as the correct one. Andrew Tanenbaum and Maarten van Steen chose the following loose characterization for describing a distributed system:
+
+"A distributed system is a collection of independent computers that appears to its users as a single coherent system" - Andrew Tanenbaum
+
+The user only needs to interact with the local computer in front of them, while the software of the local computer ensures smooth communication with the other participating computers in the distributed system.
+
+This thesis aims to make it easier for users to view distributed systems from a different perspective. Here, the viewpoint of an end user is not adopted; instead, the functional methods of protocols and their processes in distributed systems should be made comprehensible, while simultaneously making all relevant events of a distributed system transparent.
+
+To achieve this goal, a simulator was developed, particularly for teaching and learning purposes at the University of Applied Sciences Aachen. With the simulator, protocols from distributed systems with their most important influencing factors can be replicated through simulations. At the same time, there is ample room for personal experiments, with no restriction to a fixed number of protocols. It is therefore important that users are enabled to design their own protocols.
+
+

Fundamentals


+
+For basic understanding, some fundamentals are explained below. A deeper exploration will follow in later chapters.
+
+

Client/Server Model


+
+
+┌─────────────────────────────────────────────┐
+│                                             │
+│     ┌────────┐         ┌────────┐           │
+│     │ Client │◄-------►│ Server │           │
+│     └────────┘         └────────┘           │
+│                                             │
+│         Sending of Messages                 │
+│                                             │
+└─────────────────────────────────────────────┘
+
+Figure 1.1: Client/Server Model
+
+
+The simulator is based on the client/server principle. Each simulation typically consists of a participating client and a server that communicate with each other via messages (see Fig. 1.1). In complex simulations, multiple clients and/or servers can also participate.
+
+

Processes and Their Roles


+
+A distributed system is simulated using processes. Each process takes on one or more roles. For example, one process can take on the role of a client and another process the role of a server. The possibility of assigning both client and server roles to a process simultaneously is also provided. A process could also take on the roles of multiple servers and clients simultaneously. To identify a process, each one has a unique Process Identification Number (PID).
+
+

Messages


+
+In a distributed system, it must be possible to send messages. A message can be sent by a client or server process and can have any number of recipients. The content of a message depends on the protocol used. What is meant by a protocol will be covered later. To identify a message, each message has a unique Message Identification Number (NID).
+
+

Local and Global Clocks


+
+In a simulation, there is exactly one global clock. It represents the current and always correct time. A global clock never goes wrong.
+
+Additionally, each participating process has its own local clock. It represents the current time of the respective process. Unlike the global clock, local clocks can display an incorrect time. If the process time is not globally correct (not equal to the global time, or displays an incorrect time), then it was either reset during a simulation, or it is running incorrectly due to clock drift. The clock drift indicates by what factor the clock is running incorrectly. This will be discussed in more detail later.
+
+
+┌─────────────────────┐     ┌─────────────────────┐
+│    Process 1        │     │    Process 2        │
+│                     │     │                     │
+│ ┌─────────────────┐ │     │ ┌─────────────────┐ │
+│ │Server Protocol A│ │     │ │Client Protocol A│ │
+│ └─────────────────┘ │     │ └─────────────────┘ │
+│                     │     │                     │
+│ ┌─────────────────┐ │     └─────────────────────┘
+│ │Client Protocol B│ │     
+│ └─────────────────┘ │     ┌─────────────────────┐
+│                     │     │    Process 3        │
+└─────────────────────┘     │                     │
+                            │ ┌─────────────────┐ │
+                            │ │Server Protocol B│ │
+                            │ └─────────────────┘ │
+                            │                     │
+                            └─────────────────────┘
+
+Figure 1.2: Client/Server Protocols
+
+
+In addition to normal clocks, vector timestamps and Lamport's logical clocks are also of interest. For vector and Lamport times, there are no global equivalents here, unlike normal time. Concrete examples of Lamport and vector times will be covered later in Chapter 3.11.1.
+
+

Events


+
+A simulation consists of the sequential execution of finitely many events. For example, there can be an event that causes a process to send a message. A process crash event would also be conceivable. Each event occurs at a specific point in time. Events with the same occurrence time are executed directly one after another by the simulator. However, this does not hinder the simulator's users, as events are executed in parallel from their perspective.
+
+

Protocols


+
+A simulation also consists of the application of protocols. It has already been mentioned that a process can take on the roles of servers and/or clients. For each server and client role, the associated protocol must also be specified. A protocol defines how a client and a server send messages, and how they react when a message arrives. A protocol also determines what data is contained in a message. A process only processes a received message if it understands the respective protocol.
+
+In Figure 1.2, 3 processes are shown. Process 1 supports protocol "A" on the server side and protocol "B" on the client side. Process 2 supports protocol "A" on the client side and Process 3 supports protocol "B" on the server side. This means that Process 1 can communicate with Process 2 via protocol "A" and with Process 3 via protocol "B". Processes 2 and 3 are incompatible with each other and cannot process messages received from each other.
+
+Clients cannot communicate with clients, and servers cannot communicate with servers. For communication, at least one client and one server are always required. However, this restriction can be circumvented by having processes support a given protocol on both the server and client sides (see Broadcast Protocol in Chapter 3.3).
+
+

Graphical User Interface (GUI)


+
+

Simple Mode


+
+![Figure 2.1: The simulator after first launch]
+
+The simulator requires JDK 21 and can be started with the command java -jar target/ds-sim-VERSION.jar
+
+The simulator then presents itself as shown in Figure 2.1. To create a new simulation, select "New Simulation" from the "File" menu (see Fig. 2.2), after which the settings window for the new simulation appears. The individual options will be discussed in more detail later, and for now, only the default settings will be used.
+
+By default, the simulator starts in "simple mode". There is also an "expert mode", which will be discussed later.
+
+

The Menu Bar


+
+In the File menu (see Fig. 2.2), you can create new simulations or close the currently open simulation. New simulations open by default in a new tab. However, you can also open or close new simulation windows that have their own tabs. Each tab contains a simulation that is completely independent from the others. This allows any number of simulations to be run in parallel. The menu items "Open", "Save" and "Save As" are used for loading and saving simulations.
+
+![Figure 2.2: File Menu]
+
+Through the Edit menu, users can access the simulation settings, which will be discussed in more detail later. This menu also lists all participating processes for editing. If the user selects a process there, the corresponding process editor opens. This will also be discussed in more detail later. The Simulator menu offers the same options as the toolbar, which is described in the next section.
+
+Some menu items are only accessible when a simulation has already been created or loaded in the current window.
+
+![Figure 2.3: A new simulation]
+
+

The Toolbar


+
+The toolbar is located at the top left of the simulator (see Fig. 2.4). The toolbar contains the functions most frequently needed by users.
+
+The toolbar offers four different functions:
+
+![Figure 2.4: The menu line including toolbar]
+
+
+

The Visualization


+
+![Figure 2.5: Visualization of a simulation that has not yet been started]
+
+The graphical simulation visualization is located in the center right. The X-axis shows the time in milliseconds, and all participating processes are listed on the Y-axis. The demo simulation ends after exactly 15 seconds. Figure 2.5 shows 3 processes (with PIDs 1, 2, and 3), each with its own horizontal black bar. On these process bars, users can read the respective local process time. The vertical red line represents the global simulation time.
+
+![Figure 2.6: Right-click on a process bar]
+
+The process bars also serve as start and end points for messages. For example, if Process 1 sends a message to Process 2, a line is drawn from one process bar to the other. Messages that a process sends to itself are not visualized but are logged in the log window (more on this later).
+
+Another way to open a process editor is to left-click on the process bar belonging to the process. A right-click, on the other hand, opens a popup window with additional options (see Fig. 2.6). A process can only be forced to crash or be revived via the popup menu during a running simulation.
+
+In general, the number of processes can vary as desired. The simulation duration is at least 5 and at most 120 seconds. The simulation only ends when the global time reaches the specified simulation end time (here 15 seconds), not when a local process time reaches this end time.
+
+

Color Differentiation


+
+Colors help to better interpret the processes of a simulation. By default, processes (process bars) and messages are displayed with the colors listed in Table 2.1. These are only the default colors, which can be changed via the settings.
+
+
+Table 2.1: Color differentiation of processes and messages
+
+| Process Color | Meaning                                           |
+|---------------|---------------------------------------------------|
+| Black         | The simulation is not currently running           |
+| Orange        | The mouse is over the process bar                 |
+| Red           | The process has crashed                           |
+
+| Message Color | Meaning                                                                 |
+|---------------|-------------------------------------------------------------------------|
+| Green         | The message is still in transit and has not yet reached its destination |
+| Blue          | The message has successfully reached its destination                    |
+| Red           | The message was lost                                                    |
+
+
+

The Sidebar


+
+![Figure 2.7: The sidebar with empty event editor]
+
+The sidebar is used to program process events. At the top of Figure 2.7, the process to be managed is selected (here with PID 1). In this process selection, there is also the option to select "All Processes", which displays all programmed events of all processes simultaneously. "Local events" are those events that occur when a certain local time of the associated process has been reached. The event table below lists all programmed events (none present here yet) along with their occurrence times and PIDs.
+
+![Figure 2.8: The event editor with 3 programmed events]
+
+To create a new event, the user can either right-click on a process bar (see Fig. 2.6) and select "Insert local event", or select an event below the event table (see Fig. 2.9), enter the event occurrence time in the text field below, and click "Apply". For example, in Figure 2.8, three events were added: crash after 123ms, revival after 321ms, and another crash after 3000ms of the process with ID 1.
+
+![Figure 2.9: Event selection via sidebar]
+
+Right-clicking on the event editor allows you to either copy or delete all selected events. Using the Ctrl key, multiple events can be selected simultaneously. The entries in the Time and PID columns can be edited afterwards. This provides a convenient way to move already programmed events to a different time or assign them to a different process. However, users should ensure that they press the Enter key after changing the event occurrence time, otherwise the change will be ineffective.
+
+In addition to the Events tab, the sidebar has another tab called "Variables". Behind this tab is the process editor of the currently selected process (see Fig. 2.13 left). There, all variables of the process can be edited, providing another way to access a process editor.
+
+

The Log Window


+
+The log window (see Fig. 2.3, bottom) logs all occurring events in chronological order. Figure 2.10 shows the log window after creating the demo simulation with 3 participating processes. At the beginning of each log entry, the global time in milliseconds is always logged. For each process, its local times as well as the Lamport and vector timestamps are also listed. After the time information, additional details are provided, such as which message was sent with what content and which protocol it belongs to. This will be demonstrated later with examples.
+
+![Figure 2.10: The log window]
+
+
+000000ms: New Simulation
+000000ms: New Process; PID: 1; Local Time: 000000ms; Lamport time: 0; Vector time: (0,0,0)
+000000ms: New Process; PID: 2; Local Time: 000000ms; Lamport time: 0; Vector time: (0,0,0)
+000000ms: New Process; PID: 3; Local Time: 000000ms; Lamport time: 0; Vector time: (0,0,0)
+
+□ Expert mode ☑ Logging
+
+
+By deactivating the logging switch, message logging can be temporarily disabled. With logging deactivated, no new messages are written to the log window. After reactivating the switch, all omitted messages are subsequently written to the window. Deactivated logging can lead to improved simulator performance. This is due to the very slow Java implementation of the JTextArea class, which performs updates very sluggishly.
+
+

Expert Mode


+
+The simulator can be operated in two different modes: simple mode and expert mode. The simulator starts in simple mode by default, so users don't have to deal with the simulator's full functionality all at once. Simple mode is clearer but offers fewer functions. Expert mode is more suitable for experienced users and accordingly offers more flexibility. Expert mode can be activated or deactivated via the switch of the same name below the log window or via the simulation settings. Figure 2.11 shows the simulator in expert mode. When comparing expert mode with simple mode, several differences are noticeable:
+
+![Figure 2.11: The Simulator in Expert Mode]
+
+

New Functions in the Sidebar


+
+The first difference is visible in the sidebar (see Fig. 2.12). In addition to local events, global events can now also be edited. As already mentioned, local events are those events that occur when a specific local time of the associated process has been reached. Global events, on the other hand, are those events that occur when a specific global time has been reached. A global event takes the global simulation time and a local event takes the local process time as the entry criterion. Global events thus only make a difference when the local process times differ from the global time.
+
+Furthermore, the user can directly select the associated PID when programming a new event. In simple mode, the PID of the currently selected process (in the topmost ComboBox) was always used by default (here with PID 1).
+
+![Figure 2.12: The Sidebar in Expert Mode]
+
+

Lamport Time, Vector Time, and Anti-Aliasing Switches


+
+Further differences are noticeable below the log window. Among other things, there are two new switches "Lamport time" and "Vector time". If the user activates one of these two switches, the Lamport or vector timestamps are displayed in the visualization. To maintain clarity, the user can only have one of these two switches activated at the same time.
+
+The anti-aliasing switch allows the user to activate or deactivate anti-aliasing. With anti-aliasing, all graphics in the visualization are displayed with rounded edges (see [Bra03]). For performance reasons, anti-aliasing is not active by default.
+
+

The Log Filter


+
+As a simulation becomes more complex, the entries in the log window become increasingly confusing. Here it becomes increasingly difficult to keep track of all events. To counteract this, expert mode includes a log filter that makes it possible to filter only the essential data from the logs.
+
+The log filter is activated and deactivated using the associated "Filter" switch. A regular expression in Java syntax can be entered in the input line behind it. The use of regular expressions using Java is covered in [Fri06]. For example, with "PID: (1|2)" only log lines are displayed that contain either "PID: 1" or "PID: 2". All other lines that only contain "PID: 3", for example, are not displayed. With the log filter, only the log lines that match the specified regular expression are displayed. The log filter can also be activated retroactively, as already logged events are filtered again after each filter change.
+
+The log filter can also be used during a running simulation. When the filter is deactivated, all messages are displayed again. Log messages that have never been displayed due to the filter are then displayed retroactively.
+
+![Figure 2.13: The Process Editor in the Sidebar]
+
+

Events


+
+Two main types of events are distinguished: programmable events and non-programmable events. Programmable events can be programmed and edited in the event editor, and their occurrence times depend on the local process clocks or the global clock. Non-programmable events, on the other hand, cannot be programmed in the event editor and do not occur because of a specific time, but due to other circumstances such as the arrival of a message or the execution of an action due to an alarm (more on this later).
+
+

Key Features of Events:


+
+
+

Event Types Available:


+
+
+The event editor allows users to:
+
+
+**Important**: Remember to press Enter after changing event occurrence times, otherwise the changes won't take effect.
+
+

Summary


+
+The expert mode significantly extends the simulator's capabilities, providing:
+
+
+These features make the simulator more powerful for advanced distributed systems simulation while maintaining the option to work in simple mode for basic use cases.
+
+E-Mail your comments to paul@nospam.buetow.org
+
+Back to the main site
+

+Generated with Gemtexter 3.0.1-develop | +served by OpenBSD/relayd(8)+httpd(8) | +Site Mirrors +

+ + diff --git a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-6.html b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-6.html index 16d93b1b..5c7c5fc3 100644 --- a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-6.html +++ b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-6.html @@ -30,10 +30,12 @@

Introduction



@@ -41,6 +43,10 @@
Some photos here, describe why there are 2 different models of SSD drives (replication etc)

+

ZFS encryption keys


+
+

UFS on USB keys


+
 paul@f0:/ % doas camcontrol devlist
 <512GB SSD D910R170>               at scbus0 target 0 lun 0 (pass0,ada0)
@@ -57,8 +63,6 @@ paul@f1:/ % doas camcontrol devlist
 paul@f1:/ %

-

UFS Setup


-
-
paul@f0:/dev % doas zpool create -m /data zdata /dev/ada1
-paul@f0:/dev % zpool list
-NAME    SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAG    CAP  DEDUP    HEALTH  ALTROOT
-zdata   928G   432K   928G        -         -     0%     0%  1.00x    ONLINE  -
-zroot   472G  19.8G   452G        -         -     0%     4%  1.00x    ONLINE  -
-
+
paul@f0:/keys % doas zpool create -m /data zdata /dev/ada1
+paul@f0:/keys % doas zfs create -o encryption=on -o keyformat=raw -o keylocation=file:///keys/`hostname`:zdata.key zdata/enc
+paul@f0:/ % zfs list | grep zdata
+zdata                                          836K   899G    96K  /data
+zdata/enc                                      200K   899G   200K  /data/enc
+paul@f0:/keys % zfs get all zdata/enc | grep -E -i '(encryption|key)'
+zdata/enc  encryption            aes-256-gcm                               -
+zdata/enc  keylocation           file:///keys/f0.lan.buetow.org:zdata.key  local
+zdata/enc  keyformat             raw                                       -
+zdata/enc  encryptionroot        zdata/enc                                 -
+zdata/enc  keystatus             available                                 -
 

 

-
Encryption


+
Migrating Bhyve VMs to encrypted bhyve ZFS volume


 

-USB key for key location

+Run on all 3 nodes

 

 
-
paul@f0:/keys % doas chown root *
-paul@f0:/keys % doas chmod 400 *
-paul@f0:/keys % ls -ltr
-total 24
--r--------  1 root paul 16 May 25 11:56 f0.lan.buetow.org:zdata.key
--r--------  1 root paul 16 May 25 11:56 f0.lan.buetow.org:bhyve.key
--r--------  1 root paul 16 May 25 11:56 f1.lan.buetow.org:zdata.key
--r--------  1 root paul 16 May 25 11:56 f1.lan.buetow.org:bhyve.key
--r--------  1 root paul 16 May 25 11:57 f2.lan.buetow.org:zdata.key
--r--------  1 root paul 16 May 25 11:57 f2.lan.buetow.org:bhyve.key
-

-

-
-
paul@f0:/keys % doas vm init
+paul@f0:/keys % doas vm init
 paul@f0:/keys % doas reboot
 .
 .
@@ -176,12 +175,6 @@ http://www.lorenzobettini.it
 http://www.gnu.org/software/src-highlite -->
 
paul@f0:~ % doas zfs destroy -R zroot/bhyve_old
 
-paul@f0:~ % zfs get all zdata/enc | grep -E '(encryption|key)'
-zdata/enc  encryption            aes-256-gcm                               -
-zdata/enc  keylocation           file:///keys/f0.lan.buetow.org:zdata.key  local
-zdata/enc  keyformat             raw                                       -
-zdata/enc  encryptionroot        zdata/enc                                 -
-zdata/enc  keystatus             available                                 -
 paul@f0:~ % zfs get all zroot/bhyve | grep -E '(encryption|key)'
 zroot/bhyve  encryption            aes-256-gcm                               -
 zroot/bhyve  keylocation           file:///keys/f0.lan.buetow.org:bhyve.key  local
@@ -196,30 +189,59 @@ zroot/bhyve/rocky  encryptionroot        zroot/bhyve            -
 zroot/bhyve/rocky  keystatus             available              -
 

 

-
-	paul@f0:~ % zpool status
-  pool: zdata
- state: ONLINE
-config:
-
-        NAME        STATE     READ WRITE CKSUM
-        zdata       ONLINE       0     0     0
-          ada1      ONLINE       0     0     0
-
-errors: No known data errors
-
-  pool: zroot
- state: ONLINE
-config:
-
-        NAME        STATE     READ WRITE CKSUM
-        zroot       ONLINE       0     0     0
-          ada0p4    ONLINE       0     0     0
-
-errors: No known data errors
-

-
HAST


+
CARP


+

+adding to /etc/rc.conf on f0 and f1:

+ifconfig_re0_alias0="inet vhid 1 pass testpass alias 192.168.1.138/32"

+

+adding to /etc/hosts:

+

+192.168.1.138 f3s-storage-ha f3s-storage-ha.lan f3s-storage-ha.lan.buetow.org

+

+Adding on f0 and f1:

+

+paul@f0:~ % cat <<END | doas tee -a /etc/devd.conf

+notify 0 {

+        match "system"          "CARP";

+        match "subsystem"       "[0-9]+@[0-9a-z.]+";

+        match "type"            "(MASTER|BACKUP)";

+        action "/usr/local/bin/carpcontrol.sh $subsystem $type";

+};

+END

+

+next, copied that script /usr/local/bin/carpcontrol.sh and adjusted the disk to storage

+

+/boot/loader.conf add carp_load="YES"

+reboot or run doas kldload carp0 

+

+

+ZFS auto scrubbing....~?

+

+Backup of the keys on the key locations (all keys on all 3 USB keys)

+

+Other *BSD-related posts:

+

+2025-05-11 f3s: Kubernetes with FreeBSD - Part 5: WireGuard mesh network

+2025-04-05 f3s: Kubernetes with FreeBSD - Part 4: Rocky Linux Bhyve VMs

+2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts

+2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation

+2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage

+2024-04-01 KISS high-availability with OpenBSD

+2024-01-13 One reason why I love OpenBSD

+2022-10-30 Installing DTail on OpenBSD

+2022-07-30 Let's Encrypt with OpenBSD and Rex

+2016-04-09 Jails and ZFS with Puppet on FreeBSD

+

+E-Mail your comments to paul@nospam.buetow.org

+

+Back to the main site

+

+https://forums.freebsd.org/threads/hast-and-zfs-with-carp-failover.29639/

+

+

+E-Mail your comments to paul@nospam.buetow.org

 

+Back to the main site

 

 Generated with Gemtexter 3.0.1-develop |
 served by OpenBSD/relayd(8)+httpd(8) |
diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml
index 7489d470..ff9e8df8 100644
--- a/gemfeed/atom.xml
+++ b/gemfeed/atom.xml
@@ -1,11 +1,147 @@
 
 
-    2025-06-07T10:30:12+03:00
+    2025-06-22T18:57:24+03:00
     foo.zone feed
     To be in the .zone!
     
     
     https://foo.zone/
+    
+        Task Samurai
+        
+        https://foo.zone/gemfeed/2025-07-22-task-samurai.html
+        2025-06-22T18:49:11+03:00
+        
+            Paul Buetow aka snonux
+            paul@dev.buetow.org
+        
+        
Task Samurai is a fast terminal interface for Taskwarrior written in Go using the Bubble Tea framework. It displays your tasks in a table and allows you to manage them without leaving your keyboard.
+        
+            

+                
Task Samurai


+

+Published at 2025-06-22T18:49:11+03:00

+

+Task Samurai Logo

+

+
Table of Contents


+

+

+
Introduction


+

+Task Samurai is a fast terminal interface for Taskwarrior written in Go using the Bubble Tea framework. It displays your tasks in a table and allows you to manage them without leaving your keyboard.

+

+https://taskwarrior.org

+https://github.com/charmbracelet/bubbletea

+

+
Why does this exist?


+

+
    
+
  • I wanted to tinker with agentic coding. This project was entirely implemented using OpenAI Codex.
    • 
+
  • I wanted a faster UI for Taskwarrior than other options, like Vit, which is Python-based.
    • 
+
  • I wanted something built with Bubble Tea, but I never had time to dive deep into it.
    • 
+
  • I wanted to build a toy project (like Task Samurai) first, before tackling the big ones, to get started with agentic coding.
    • 
+


+Given the current industry trend and the rapid advancements in technology, it has become clear that experimenting with AI-assisted coding tools is almost a necessity to stay relevant. Embracing these new developments doesn't mean abandoning traditional coding; instead, it means integrating new capabilities into your workflow to stay ahead in a fast-evolving field.

+

+
How it works


+

+Task Samurai invokes the task command to read and modify tasks. The tasks are displayed in a Bubble Tea table, where each row represents a task. Hotkeys trigger Taskwarrior commands such as starting, completing or annotating tasks. The UI refreshes automatically after each action, so the table is always up to date.

+

+Task Samurai Screenshot

+

+
Lessons Learned from Building Task Samurai with Agentic Coding


+

+If you've ever wanted to supercharge your dev speed—or just throw a fireworks display in your terminal—here's a peek behind the scenes of building Task Samurai. This terminal interface for Taskwarrior was developed entirely through agentic coding by me, leveraging OpenAI Codex to do all the heavy lifting (and sometimes some cleanup afterwards). The project name might be snappy, but it was the iterative, semi-automated workflow that made the impact.

+

+As a side note, I was trying out OpenAI Codex because I regularly run out of Claude Code CLI (another agentic coding tool I am trying out currently) credits (it still happens!), but Codex was still available to me. So, I seized the opportunity to push agentic coding a bit more.

+

+
How It Went Down


+

+Task Samurai's codebase came together quickly: the entire Git history spans from June 19 to 22, 2025, culminating in 179 commits. Here are the broad strokes:

+

+
    
+
  • June 19: Scaffolded the Go boilerplate, set up tests, integrated the Bubble Tea UI framework, and got the first table views showing up.
    • 
+
  • June 20: (The big one—120 commits!) Added hotkeys, colourized tasks, annotation support, undo/redo, and, for fun, fireworks on quit (which never worked and got removed at a later point). This is where most of the bugs, merges, and fast-paced changes happen.
    • 
+
  • June 21: Refined searching, theming, and column sizing and documented all those hotkeys. Numerous tweaks to make the UI cleaner and more user-friendly.
    • 
+
  • June 22: Final touches—added screenshots, polished the logo, fixed module paths… and then it was a wrap.
    • 
+


+Most big breakthroughs (and bug introductions) came during that middle day of intense iteration. The latter stages were all about smoothing out the rough edges.

+

+
What Went Wrong


+

+Going agentic isn't all smooth sailing. Here are the hiccups I ran into, plus a few hard-earned lessons:

+

+
    
+
  • Merge Floods: Every minor feature or fix existed on its branch, so merging was a constant process. It kept progress flowing but also drowned the committed history in noise and the occasional conflict.
    • 
+
  • Fixes on Fixes: Features like "fireworks on exit" had chains of "fix exit," "fix cell selection," etc. Sometimes, new additions introduced bugs that needed rapid patching.
    • 
+


+
Patterns That Helped


+

+Despite the chaos, a few strategies kept things moving:

+

+
    
+
  • Scaffolding First: I started with the basic table UI and command wrappers, then layered on features—never the other way around.
    • 
+
  • Tiny PRs: Small, atomic merges meant feedback came fast (and so did fixes).
    • 
+
  • Tests Matter: A solid base of unit tests for task manipulations kept things from breaking entirely when experimenting.
    • 
+
  • Live Documentation: Documentation, such as the README, is updated regularly to reflect all the hotkey and feature changes.
    • 
+


+
What I Learned Using Agentic Coding


+

+Stepping into agentic coding with Codex as my "pair programmer" was a genuine shift. I learned a ton—not just about automating code generation, but also about how you have to tightly steer, guide, and audit every line as things move at breakneck speed. I must admit, I sometimes lost track of what all the generated code was actually doing. But as the features seemed to work after a few iterations, I was satisfied.

+

+Discussing requirements with Codex forced me to clarify features and spot logical pitfalls earlier. All those fast iterations meant I was constantly coaxing more helpful, less ambiguous code out of the model—making me rethink how to break features into clear, testable steps. I now see agentic coding not just as a productivity tool but also as a learning accelerator.

+

+
How Much Time Did I Save?


+

+Here's the million-dollar (or many hours saved) question: Did it buy me speed?

+

+Let's do some back-of-the-envelope math:

+

+
    
+
  • Say each commit takes Codex 5 minutes to generate, and you need to review/guide 179 commits = about *6 hours of active development*.
    • 
+
  • If you coded it all yourself, including all the bug fixes, features, design, and documentation, you might spend *10–20 hours*.
    • 
+
  • That's a potential savings, so what's usually weeks of work got compressed into just a few frantic days.
    • 
+


+
Where and how to get it


+

+Go to:

+

+https://codeberg.org/snonux/tasksamurai

+

+And follow the README.md!

+

+
Wrapping Up


+

+Building Task Samurai with agentic coding was a wild ride—rapid feature growth, plenty of churns, countless fast fixes, and more merge commits I'd expected. The big lessons? Keep the iterations short, keep tests and documentation concise, and review and refine for final polish at the end. Even with the bumps along the way, shipping a polished terminal UI in days instead of weeks is a testament to the raw power (and some hazards) of agentic development.

+

+While working on Task Samuray, there were times I genuinely missed manual coding and the satisfaction that comes from writing every line yourself, debugging issues through sheer logic, and crafting solutions from scratch. However, this is the direction in which the industry seems to be shifting, unfortunately. If applied correctly, AI will boost performance, and if you don't use AI, your next performance review may be awkward.

+

+If you're considering going agentic, be prepared for a sprint, keep your toolkit sharp, and be ready to learn a lot along the way.

+

+Personally, I am not sure whether I like where the industry is going with agentic coding. I love "traditional" coding, and with agentic coding you operate at a higher level and don't interact directly with code as often, which I would miss. I think that in the future, designing, reviewing, and being able to read and understand code will be more important than writing code by hand.

+

+Do you have any thoughts on that? I hope, I am partially wrong at least.

+

+E-Mail your comments to paul@nospam.buetow.org :-)

+

+Back to the main site

+            

+        
+    
     
         'A Monk's Guide to Happiness' book notes
         
@@ -20,6 +156,8 @@
             

                 
"A Monk's Guide to Happiness" book notes


 

+Published at 2025-06-07T10:30:11+03:00

+

 These are my personal book notes from Gelong Thubten's "A Monk's Guide to Happiness: Meditation in the 21st century." They are for my own reference, but I hope they might be useful to you as well.

 

 
Table of Contents


@@ -103,6 +241,19 @@
 

 E-Mail your comments to paul@nospam.buetow.org :-)

 

+Other book notes of mine are:

+

+2025-06-07 "A Monk's Guide to Happiness" book notes (You are currently reading this)

+2025-04-19 "When: The Scientific Secrets of Perfect Timing" book notes

+2024-10-24 "Staff Engineer" book notes

+2024-07-07 "The Stoic Challenge" book notes

+2024-05-01 "Slow Productivity" book notes

+2023-11-11 "Mind Management" book notes

+2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes

+2023-05-06 "The Obstacle is the Way" book notes

+2023-04-01 "Never split the difference" book notes

+2023-03-16 "The Pragmatic Programmer" book notes

+

 Back to the main site

             

         
@@ -3969,93 +4120,14 @@ Jan 26 17:36:32 f2 apcupsd[2159]: apcupsd shutdown succeeded
 

 So I put this into my zsh dotfiles (in some editor.zsh.source in my ~ directory):

 

-
-
export EDITOR=hx
-export VISUAL=$EDITOR
-export GIT_EDITOR=$EDITOR
-export HELIX_CONFIG_DIR=$HOME/.config/helix
-
-editor::helix::random_theme () {
-    # May add more theme search paths based on OS. This one is
-    # for Fedora Linux, but there is also MacOS, etc.
-    local -r theme_dir=/usr/share/helix/runtime/themes
-    if [ ! -d $theme_dir ]; then
-        echo "Helix theme dir $theme_dir doesnt exist"
-        return 1
-    fi
-
-    local -r config_file=$HELIX_CONFIG_DIR/config.toml
-    local -r random_theme="$(basename "$(ls $theme_dir \
-        | grep -v random.toml | grep .toml | sort -R \
-        | head -n 1)" | cut -d. -f1)"
-
-    sed "/^theme =/ { s/.*/theme = \"$random_theme\"/; }" \
-        $config_file > $config_file.tmp && 
-        mv $config_file.tmp $config_file
-}
-
-if [ -f $HELIX_CONFIG_DIR/config.toml ]; then
-    editor::helix::random_theme
-fi
-

 

 So every time I open a new terminal or shell, editor::helix::random_theme gets called, which randomly selects a theme from all installed ones and updates the helix config accordingly.

 

-
-
[paul@earth] ~ % editor::helix::random_theme
-[paul@earth] ~ % head -n 1 ~/.config/helix/config.toml
-theme = "jellybeans"
-[paul@earth] ~ % editor::helix::random_theme
-[paul@earth] ~ % head -n 1 ~/.config/helix/config.toml
-theme = "rose_pine"
-[paul@earth] ~ % editor::helix::random_theme
-[paul@earth] ~ % head -n 1 ~/.config/helix/config.toml
-theme = "noctis"
-[paul@earth] ~ %
-

 

 
A better version


 

 Update 2024-12-18: This is an improved version, which works cross platform (e.g., also on MacOS) and multiple theme directories:

 

-
-
export EDITOR=hx
-export VISUAL=$EDITOR
-export GIT_EDITOR=$EDITOR
-export HELIX_CONFIG_DIR=$HOME/.config/helix
-
-editor::helix::theme::get_random () {
-    for dir in $(hx --health \
-        | awk '/^Runtime directories/ { print $3 }' | tr ';' ' '); do
-        if [ -d $dir/themes ]; then
-            ls $dir/themes
-        fi
-    done | grep -F .toml | sort -R | head -n 1 | cut -d. -f1
-}
-
-editor::helix::theme::set () {
-    local -r theme="$1"; shift
-
-    local -r config_file=$HELIX_CONFIG_DIR/config.toml
-
-    sed "/^theme =/ { s/.*/theme = \"$theme\"/; }" \
-        $config_file > $config_file.tmp && 
-        mv $config_file.tmp $config_file
-}
-
-if [ -f $HELIX_CONFIG_DIR/config.toml ]; then
-    editor::helix::theme::set $(editor::helix::theme::get_random)
-fi
-

 

 I hope you had some fun. E-Mail your comments to paul@nospam.buetow.org :-)

 

@@ -10418,120 +10490,6 @@ The remaining content of the Gemtext file...
 2021-06-05 Gemtexter - One Bash script to rule it all

 2021-04-24 Welcome to the Geminispace

 

-Back to the main site

-            
-        
-    
-    
-        'The Pragmatic Programmer' book notes
-        
-        https://foo.zone/gemfeed/2023-03-16-the-pragmatic-programmer-book-notes.html
-        2023-03-16T00:55:20+02:00
-        
-            Paul Buetow aka snonux
-            paul@dev.buetow.org
-        
-        These are my personal takeaways after reading 'The Pragmatic Programmer' by David Thomas and Andrew Hunt. Note that the book contains much more knowledge wisdom and that these notes only contain points I personally found worth writing down. This is mainly for my own use, but you might find it helpful too.
-        
-            

-                
"The Pragmatic Programmer" book notes


-

-Published at 2023-03-16T00:55:20+02:00

-

-These are my personal takeaways after reading "The Pragmatic Programmer" by David Thomas and Andrew Hunt. Note that the book contains much more knowledge wisdom and that these notes only contain points I personally found worth writing down. This is mainly for my own use, but you might find it helpful too.

-

-
-         ,..........   ..........,
-     ,..,'          '.'          ',..,
-    ,' ,'            :            ', ',
-   ,' ,'             :             ', ',
-  ,' ,'              :              ', ',
- ,' ,'............., : ,.............', ',
-,'  '............   '.'   ............'  ',
- '''''''''''''''''';''';''''''''''''''''''
-                    '''
-

-

-Think about your work while doing it - every day on every project. Have a feeling of continuous improvement. 

-

-
    
-
  • Be a realist.
    • 
-
  • Smell challenges.
    • 
-
  • Care about your craft.
    • 
-
  • Code can always be flawed, but it can meet the requirements.
    • 
-
  • You should be proud of your code, though.
    • 
-


-No one writes perfect code, including you. However:

-

-
    
-
  • Paranoia is good thinking.
    • 
-
  • Practice defensive programming and crash early.
    • 
-
  • Crashing is often the best thing you can do. 
    • 
-
  • Changes should be reversible.
    • 
-


-Erlang: Defensive programming is a waste of time. Let it crash. "This can never happen" - don't practise that kind of self-deception when programming. 

-

-Leave assertions in the code, even in production. Only leave out the assertions causing the performance issues.

-

-Take small steps, always. Get feedback, too, for each of the steps the code does. Avoid fortune telling. If you have to involve in it, then the step is too large.

-

-Decouple the code (e.g. OOP or functional programming). Prefer interfaces for types and mixins for a class extension over class inheritance.

-

-
    
-
  • Refactor now and not later.
    • 
-
  • Later, it will be even more painful.
    • 
-


-Don't think outside the box. Find the box. The box is more extensive than you think. Think about the hard problem at hand. Do you have to do it a certain way, or do you have to do it at all?

-

-Do what works and not what's fashionable. E.g. does SCRUM make sense? The goal is to deliver deliverables and not to "become" agile.

-

-
Continuous learning


-

-Add new tools to your repertoire every day and keep the momentum up. Learning new things is your most crucial aspect. Invest regularly in your knowledge portfolio. The learning process extends your thinking. It does not matter if you will never use it.

-

-
    
-
  • Learn a new programming language every year.
    • 
-
  • Read a technical book every month.
    • 
-
  • Take courses.
    • 
-


-Think critically about everything you learn. Use paper for your notes. There is something special about it.

-

-
Stay connected


-

-It's your life, and you own it. Bruce Lee once said: 

-

-"I am not on the world to life after your expectations, neither are you to life after mine."

-

-
    
-
  • Go to meet-ups and actively engage.
    • 
-
  • Stay current.
    • 
-
  • Dealing with computers is hard. Dealing with people is harder. 
    • 
-


-It's your life. Share it, celebrate it, be proud and have fun.

-

-
The story of stone soup


-

-How to motivate others to contribute something (e.g. ideas to a startup):

-

-A kindly, old stranger was walking through the land when he came upon a village. As he entered, the villagers moved towards their homes, locking doors and windows. The stranger smiled and asked, why are you all so frightened. I am a simple traveler, looking for a soft place to stay for the night and a warm place for a meal. "There's not a bite to eat in the whole province," he was told. "We are weak and our children are starving. Better keep moving on." "Oh, I have everything I need," he said. "In fact, I was thinking of making some stone soup to share with all of you." He pulled an iron cauldron from his cloak, filled it with water, and began to build a fire under it. Then, with great ceremony, he drew an ordinary-looking stone from a silken bag and dropped it into the water. By now, hearing the rumor of food, most of the villagers had come out of their homes or watched from their windows. As the stranger sniffed the "broth" and licked his lips in anticipation, hunger began to overcome their fear. "Ahh," the stranger said to himself rather loudly, "I do like a tasty stone soup. Of course, stone soup with cabbage -- that's hard to beat." Soon a villager approached hesitantly, holding a small cabbage he'd retrieved from its hiding place, and added it to the pot. "Wonderful!!" cried the stranger. "You know, I once had stone soup with cabbage and a bit of salt beef as well, and it was fit for a king." The village butcher managed to find some salt beef . . .  And so it went, through potatoes, onions, carrots, mushrooms, and so on, until there was indeed a delicious meal for everyone in the village to share. The village elder offered the stranger a great deal of money for the magic stone, but he refused to sell it and traveled on the next day. As he left, the stranger came upon a group of village children standing near the road. He gave the silken bag containing the stone to the youngest child, whispering to a group, "It was not the stone, but the villagers that had performed the magic." 

-

-By working together, everyone contributes what they can, achieving a greater good together.

-

-E-Mail your comments to paul@nospam.buetow.org :-)

-

-Other book notes of mine are:

-

-2025-06-07 "A Monk's Guide to Happiness" book notes

-2025-04-19 "When: The Scientific Secrets of Perfect Timing" book notes

-2024-10-24 "Staff Engineer" book notes

-2024-07-07 "The Stoic Challenge" book notes

-2024-05-01 "Slow Productivity" book notes

-2023-11-11 "Mind Management" book notes

-2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes

-2023-05-06 "The Obstacle is the Way" book notes

-2023-04-01 "Never split the difference" book notes

-2023-03-16 "The Pragmatic Programmer" book notes (You are currently reading this)

-

 Back to the main site

             

         
diff --git a/gemfeed/index.html b/gemfeed/index.html
index 3634eead..2c897a34 100644
--- a/gemfeed/index.html
+++ b/gemfeed/index.html
@@ -15,6 +15,7 @@
 

 
To be in the .zone!


 

+2025-07-22 - Task Samurai

 2025-06-07 - 'A Monk's Guide to Happiness' book notes

 2025-05-11 - f3s: Kubernetes with FreeBSD - Part 5: WireGuard mesh network

 2025-05-02 - Terminal multiplexing with tmux - Fish edition

diff --git a/gemfeed/task-samurai/logo.png b/gemfeed/task-samurai/logo.png
new file mode 100644
index 00000000..04363b99
Binary files /dev/null and b/gemfeed/task-samurai/logo.png differ
diff --git a/gemfeed/task-samurai/screenshot.png b/gemfeed/task-samurai/screenshot.png
new file mode 100644
index 00000000..9ee1e618
Binary files /dev/null and b/gemfeed/task-samurai/screenshot.png differ
diff --git a/index.html b/index.html
index afcaa0fc..4c8d25ad 100644
--- a/index.html
+++ b/index.html
@@ -13,7 +13,7 @@
 

 
Hello!


 

-This site was generated at 2025-06-07T10:30:12+03:00 by Gemtexter

+This site was generated at 2025-06-22T18:57:24+03:00 by Gemtexter

 

 Welcome to the ...

 

@@ -51,6 +51,7 @@
 

 
Posts


 

+2025-07-22 - Task Samurai

 2025-06-07 - 'A Monk's Guide to Happiness' book notes

 2025-05-11 - f3s: Kubernetes with FreeBSD - Part 5: WireGuard mesh network

 2025-05-02 - Terminal multiplexing with tmux - Fish edition

diff --git a/uptime-stats.html b/uptime-stats.html
index 1867eea5..27f90cba 100644
--- a/uptime-stats.html
+++ b/uptime-stats.html
@@ -13,7 +13,7 @@
 

 
My machine uptime stats


 

-This site was last updated at 2025-06-07T10:30:12+03:00

+This site was last updated at 2025-06-22T18:57:24+03: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.

 

@@ -36,7 +36,7 @@
 +-----+----------------+-------+------------------------------+
 |  1. |  alphacentauri |   671 |      FreeBSD 11.4-RELEASE-p7 |
 |  2. |           mars |   207 |          Linux 3.2.0-4-amd64 |
-|  3. |         *earth |   185 | Linux 6.14.6-300.fc42.x86_64 |
+|  3. |         *earth |   188 | Linux 6.14.6-300.fc42.x86_64 |
 |  4. |       callisto |   153 |  Linux 4.0.4-303.fc22.x86_64 |
 |  5. |       dionysus |   136 |     FreeBSD 13.0-RELEASE-p11 |
 |  6. |      tauceti-e |   120 |          Linux 3.2.0-4-amd64 |
@@ -44,16 +44,16 @@
 |  8. |        *uranus |    59 |                  NetBSD 10.1 |
 |  9. |          pluto |    51 |          Linux 3.2.0-4-amd64 |
 | 10. |      mega15289 |    50 |                Darwin 23.4.0 |
-| 11. |   *mega-m3-pro |    46 |                Darwin 24.5.0 |
-| 12. |          *t450 |    43 |         FreeBSD 14.2-RELEASE |
-| 13. |    *fishfinger |    43 |                  OpenBSD 7.6 |
-| 14. |         phobos |    40 |      Linux 3.4.0-CM-g1dd7cdf |
-| 15. |       mega8477 |    40 |                Darwin 13.4.0 |
+| 11. |   *mega-m3-pro |    49 |                Darwin 24.5.0 |
+| 12. |    *fishfinger |    43 |                  OpenBSD 7.6 |
+| 13. |          *t450 |    43 |         FreeBSD 14.2-RELEASE |
+| 14. |       mega8477 |    40 |                Darwin 13.4.0 |
+| 15. |         phobos |    40 |      Linux 3.4.0-CM-g1dd7cdf |
 | 16. |      *blowfish |    38 |                  OpenBSD 7.6 |
 | 17. |            sun |    33 |     FreeBSD 10.3-RELEASE-p24 |
 | 18. |            *f2 |    25 |      FreeBSD 14.2-RELEASE-p1 |
-| 19. |           moon |    20 |      FreeBSD 14.0-RELEASE-p3 |
-| 20. |            *f1 |    20 |      FreeBSD 14.2-RELEASE-p1 |
+| 19. |            *f1 |    20 |      FreeBSD 14.2-RELEASE-p1 |
+| 20. |           moon |    20 |      FreeBSD 14.0-RELEASE-p3 |
 +-----+----------------+-------+------------------------------+
 

 

@@ -68,7 +68,7 @@
 |  1. |         vulcan |   4 years, 5 months, 6 days | Linux 3.10.0-1160.81.1.el7.x86_64 |
 |  2. |            sun |  3 years, 9 months, 26 days |          FreeBSD 10.3-RELEASE-p24 |
 |  3. |        *uranus |   3 years, 9 months, 5 days |                       NetBSD 10.1 |
-|  4. |         *earth |  3 years, 5 months, 27 days |      Linux 6.14.6-300.fc42.x86_64 |
+|  4. |         *earth |   3 years, 6 months, 8 days |      Linux 6.14.6-300.fc42.x86_64 |
 |  5. |      *blowfish |  3 years, 5 months, 16 days |                       OpenBSD 7.6 |
 |  6. |          uugrn |   3 years, 5 months, 5 days |           FreeBSD 11.2-RELEASE-p4 |
 |  7. |      deltavega |  3 years, 1 months, 21 days | Linux 3.10.0-1160.11.1.el7.x86_64 |
@@ -82,7 +82,7 @@
 | 15. |          host0 |   1 years, 3 months, 9 days |          FreeBSD 6.2-RELEASE-p5   |
 | 16. |      *makemake |   1 years, 3 months, 5 days |       Linux 6.9.9-200.fc40.x86_64 |
 | 17. |      tauceti-e |  1 years, 2 months, 20 days |               Linux 3.2.0-4-amd64 |
-| 18. |   *mega-m3-pro |   1 years, 1 months, 3 days |                     Darwin 24.5.0 |
+| 18. |   *mega-m3-pro |  1 years, 1 months, 13 days |                     Darwin 24.5.0 |
 | 19. |       callisto | 0 years, 10 months, 31 days |       Linux 4.0.4-303.fc22.x86_64 |
 | 20. |  alphacentauri | 0 years, 10 months, 28 days |           FreeBSD 11.4-RELEASE-p7 |
 +-----+----------------+-----------------------------+-----------------------------------+
@@ -98,7 +98,7 @@
 +-----+----------------+-------+-----------------------------------+
 |  1. |        *uranus |   342 |                       NetBSD 10.1 |
 |  2. |         vulcan |   275 | Linux 3.10.0-1160.81.1.el7.x86_64 |
-|  3. |         *earth |   240 |      Linux 6.14.6-300.fc42.x86_64 |
+|  3. |         *earth |   242 |      Linux 6.14.6-300.fc42.x86_64 |
 |  4. |            sun |   238 |          FreeBSD 10.3-RELEASE-p24 |
 |  5. |      *blowfish |   218 |                       OpenBSD 7.6 |
 |  6. |          uugrn |   211 |           FreeBSD 11.2-RELEASE-p4 |
@@ -138,7 +138,7 @@
 |  9. |           mars |  1 years, 2 months, 10 days |          Linux 3.2.0-4-amd64 |
 | 10. |      tauceti-e |  0 years, 12 months, 9 days |          Linux 3.2.0-4-amd64 |
 | 11. |         sirius |  0 years, 8 months, 20 days |   Linux 2.6.32-042stab111.12 |
-| 12. |         *earth |  0 years, 6 months, 19 days | Linux 6.14.6-300.fc42.x86_64 |
+| 12. |         *earth |  0 years, 6 months, 20 days | Linux 6.14.6-300.fc42.x86_64 |
 | 13. |         deimos |  0 years, 5 months, 15 days |  Linux 4.4.5-300.fc23.x86_64 |
 | 14. |            *f0 |  0 years, 4 months, 20 days |      FreeBSD 14.2-RELEASE-p1 |
 | 15. |            *f2 |  0 years, 4 months, 19 days |      FreeBSD 14.2-RELEASE-p1 |
@@ -163,7 +163,7 @@
 |  3. |  alphacentauri |  6 years, 9 months, 13 days |           FreeBSD 11.4-RELEASE-p7 |
 |  4. |         vulcan |   4 years, 5 months, 6 days | Linux 3.10.0-1160.81.1.el7.x86_64 |
 |  5. |      *makemake |   4 years, 4 months, 7 days |       Linux 6.9.9-200.fc40.x86_64 |
-|  6. |         *earth | 3 years, 11 months, 12 days |      Linux 6.14.6-300.fc42.x86_64 |
+|  6. |         *earth | 3 years, 11 months, 25 days |      Linux 6.14.6-300.fc42.x86_64 |
 |  7. |            sun |  3 years, 10 months, 2 days |          FreeBSD 10.3-RELEASE-p24 |
 |  8. |      *blowfish |  3 years, 5 months, 17 days |                       OpenBSD 7.6 |
 |  9. |          uugrn |   3 years, 5 months, 5 days |           FreeBSD 11.2-RELEASE-p4 |
@@ -191,7 +191,7 @@
 +-----+----------------+-------+
 |  1. |  FreeBSD 10... |   551 |
 |  2. |     Linux 3... |   550 |
-|  3. |    *Linux 6... |   165 |
+|  3. |    *Linux 6... |   168 |
 |  4. |     Linux 5... |   162 |
 |  5. |     Linux 4... |   161 |
 |  6. |  FreeBSD 11... |   153 |
@@ -202,13 +202,13 @@
 | 11. |   Darwin 23... |    33 |
 | 12. |   FreeBSD 5... |    25 |
 | 13. |     Linux 2... |    22 |
-| 14. |  *Darwin 24... |    18 |
+| 14. |  *Darwin 24... |    21 |
 | 15. |   Darwin 21... |    17 |
 | 16. |   Darwin 15... |    15 |
 | 17. |   Darwin 22... |    12 |
 | 18. |   Darwin 18... |    11 |
-| 19. |   FreeBSD 7... |    10 |
-| 20. |   OpenBSD 4... |    10 |
+| 19. |   OpenBSD 4... |    10 |
+| 20. |   FreeBSD 6... |    10 |
 +-----+----------------+-------+

@@ -224,7 +224,7 @@ | 2. | *OpenBSD 7... | 6 years, 9 months, 24 days | | 3. | FreeBSD 10... | 5 years, 9 months, 9 days | | 4. | Linux 5... | 4 years, 10 months, 21 days | -| 5. | *Linux 6... | 2 years, 8 months, 23 days | +| 5. | *Linux 6... | 2 years, 9 months, 5 days | | 6. | Linux 4... | 2 years, 7 months, 22 days | | 7. | FreeBSD 11... | 2 years, 4 months, 28 days | | 8. | Linux 2... | 1 years, 11 months, 21 days | @@ -238,7 +238,7 @@ | 16. | Darwin 22... | 0 years, 6 months, 22 days | | 17. | Darwin 15... | 0 years, 6 months, 15 days | | 18. | FreeBSD 5... | 0 years, 5 months, 18 days | -| 19. | *Darwin 24... | 0 years, 5 months, 6 days | +| 19. | *Darwin 24... | 0 years, 5 months, 16 days | | 20. | FreeBSD 13... | 0 years, 4 months, 2 days | +-----+----------------+------------------------------+ @@ -255,7 +255,7 @@ | 2. | *OpenBSD 7... | 435 | | 3. | FreeBSD 10... | 406 | | 4. | Linux 5... | 317 | -| 5. | *Linux 6... | 183 | +| 5. | *Linux 6... | 186 | | 6. | Linux 4... | 175 | | 7. | FreeBSD 11... | 159 | | 8. | Linux 2... | 121 | @@ -268,9 +268,9 @@ | 15. | Darwin 18... | 32 | | 16. | Darwin 22... | 30 | | 17. | Darwin 15... | 29 | -| 18. | *Darwin 24... | 25 | -| 19. | FreeBSD 13... | 25 | -| 20. | FreeBSD 5... | 25 | +| 18. | *Darwin 24... | 27 | +| 19. | FreeBSD 5... | 25 | +| 20. | FreeBSD 13... | 25 | +-----+----------------+-------+
@@ -282,9 +282,9 @@ +-----+------------+-------+ | Pos | KernelName | Boots | +-----+------------+-------+ -| 1. | *Linux | 1060 | +| 1. | *Linux | 1063 | | 2. | *FreeBSD | 944 | -| 3. | *Darwin | 151 | +| 3. | *Darwin | 154 | | 4. | *OpenBSD | 101 | | 5. | *NetBSD | 1 | +-----+------------+-------+ @@ -298,10 +298,10 @@ +-----+------------+-----------------------------+ | Pos | KernelName | Uptime | +-----+------------+-----------------------------+ -| 1. | *Linux | 27 years, 9 months, 15 days | +| 1. | *Linux | 27 years, 9 months, 28 days | | 2. | *FreeBSD | 11 years, 5 months, 3 days | | 3. | *OpenBSD | 7 years, 5 months, 5 days | -| 4. | *Darwin | 4 years, 8 months, 24 days | +| 4. | *Darwin | 4 years, 9 months, 3 days | | 5. | *NetBSD | 0 years, 1 months, 1 days | +-----+------------+-----------------------------+ @@ -314,10 +314,10 @@ +-----+------------+-------+ | Pos | KernelName | Score | +-----+------------+-------+ -| 1. | *Linux | 1842 | +| 1. | *Linux | 1845 | | 2. | *FreeBSD | 799 | | 3. | *OpenBSD | 474 | -| 4. | *Darwin | 308 | +| 4. | *Darwin | 310 | | 5. | *NetBSD | 2 | +-----+------------+-------+ -- cgit v1.2.3