summaryrefslogtreecommitdiff
path: root/gemfeed
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2024-11-17 18:03:29 +0200
committerPaul Buetow <paul@buetow.org>2024-11-17 18:03:29 +0200
commit1aaedef7810cc6740ebf4956cdcd70cbd331cbdd (patch)
tree06f44039b42aa3bbb06c24b723bf983f99893834 /gemfeed
parent7c9b6beb471674c7d49e699da104ae8a2cf27c9d (diff)
Update content for gemtext
Diffstat (limited to 'gemfeed')
-rw-r--r--gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi2
-rw-r--r--gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi.tpl2
-rw-r--r--gemfeed/atom.xml4
3 files changed, 4 insertions, 4 deletions
diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi
index 07500032..75e7fb24 100644
--- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi
+++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi
@@ -79,7 +79,7 @@ On two of the three physical FreeBSD nodes, I will add a second SSD drive to eac
A virtual IP (VIP) will point to the master node. When the master node goes down, the VIP will failover to the standby node, where the ZFS pool will be mounted. An NFS server will listen to both nodes. k3s will use the VIP to access the NFS shares.
-=> https://wiki.freebsd.org/HighlyAvailableStorage
+=> https://wiki.freebsd.org/HighlyAvailableStorage FreeBSD Wiki: Highly Available Storage
You can think of DRBD being the Linux equivalent to FreeBSD's HAST.
diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi.tpl b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi.tpl
index b346a023..27e48c56 100644
--- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi.tpl
+++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi.tpl
@@ -64,7 +64,7 @@ On two of the three physical FreeBSD nodes, I will add a second SSD drive to eac
A virtual IP (VIP) will point to the master node. When the master node goes down, the VIP will failover to the standby node, where the ZFS pool will be mounted. An NFS server will listen to both nodes. k3s will use the VIP to access the NFS shares.
-=> https://wiki.freebsd.org/HighlyAvailableStorage
+=> https://wiki.freebsd.org/HighlyAvailableStorage FreeBSD Wiki: Highly Available Storage
You can think of DRBD being the Linux equivalent to FreeBSD's HAST.
diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml
index 56de2db8..cd0f9727 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>2024-11-17T10:14:02+02:00</updated>
+ <updated>2024-11-17T18:02:52+02:00</updated>
<title>foo.zone feed</title>
<subtitle>To be in the .zone!</subtitle>
<link href="gemini://foo.zone/gemfeed/atom.xml" rel="self" />
@@ -101,7 +101,7 @@
<br />
<span>A virtual IP (VIP) will point to the master node. When the master node goes down, the VIP will failover to the standby node, where the ZFS pool will be mounted. An NFS server will listen to both nodes. k3s will use the VIP to access the NFS shares.</span><br />
<br />
-<a class='textlink' href='https://wiki.freebsd.org/HighlyAvailableStorage'>https://wiki.freebsd.org/HighlyAvailableStorage</a><br />
+<a class='textlink' href='https://wiki.freebsd.org/HighlyAvailableStorage'>FreeBSD Wiki: Highly Available Storage</a><br />
<br />
<span>You can think of DRBD being the Linux equivalent to FreeBSD&#39;s HAST.</span><br />
<br />