From ae24d9a8869c497537839f330384cbadb2cf687c Mon Sep 17 00:00:00 2001
From: Mitja Felicijan <mitja.felicijan@gmail.com>
Date: Tue, 31 Oct 2023 10:17:43 +0100
Subject: Updated theme

---
 ...ringing-all-of-my-projects-together-under-one-umbrella.html | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

(limited to 'public/bringing-all-of-my-projects-together-under-one-umbrella.html')

diff --git a/public/bringing-all-of-my-projects-together-under-one-umbrella.html b/public/bringing-all-of-my-projects-together-under-one-umbrella.html
index 3761287..3bebf92 100755
--- a/public/bringing-all-of-my-projects-together-under-one-umbrella.html
+++ b/public/bringing-all-of-my-projects-together-under-one-umbrella.html
@@ -159,11 +159,11 @@ in the file.</ul><pre tabindex=0 style=background-color:#fff><code><span style=d
 </span></span><span style=display:flex><span>WantedBy=<span style=color:#a31515>multi-user.target</span>
 </span></span></code></pre><ul><li>You might need to reload systemd with <code>systemctl daemon-reload</code>.<li>Then I enabled the service with <code>systemctl enable caddy.service</code>.<li>And then I started the service with <code>systemctl start caddy.service</code>.</ul><p>This was about all that I needed to do to get it running. Now I can easily add
 new subdomains and domains to the main configuration file and be done with
-it. No manual Let's Encrypt shenanigans needed.</div></article></main><section><hr><h2>Posts from blogs I follow around the net</h2><ul><li><a href=https://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSWhyNotDirectoryToFilesystem target=_blank rel=noopener>One reason that ZFS can't turn a directory into a filesystem</a> — <a href=https://utcc.utoronto.ca/~cks/space/blog/>Chris's Wiki :: blog</a><div>One of the wishes that I and other people frequently have for ZFS
-is the ability to take an existing directory (and everything
-underneath it) in a ZFS filesystem and turn it into a sub-filesystem
-of its own. One reason for wanting this is that a number of things
-are set and controlled on a per-filesyst…<li><a href=http://www.landley.net/notes-2023.html#28-10-2023 target=_blank rel=noopener>October 28, 2023</a> — <a href=http://www.landley.net/notes-2023.html>Rob Landley's Blog Thing for 2023</a><div>Oh good grief, two of my least favorite licensing people, Larry Rosen
+it. No manual Let's Encrypt shenanigans needed.</div></article></main><section><hr><h2>Posts from blogs I follow around the net</h2><ul><li><a href=https://utcc.utoronto.ca/~cks/space/blog/linux/NFSv4ServerLockClients target=_blank rel=noopener>Finding which NFSv4 client owns a lock on a Linux NFS(v4) server</a> — <a href=https://utcc.utoronto.ca/~cks/space/blog/>Chris's Wiki :: blog</a><div>A while back I wrote an entry about finding which NFS client owns
+a lock on a Linux NFS server, which turned
+out to be specific to NFS v3 (which I really should have seen coming,
+since it involved NLM and lockd). Finding the NFS v4 client that
+owns a lock is, depending on your perspective, either simpl…<li><a href=http://www.landley.net/notes-2023.html#28-10-2023 target=_blank rel=noopener>October 28, 2023</a> — <a href=http://www.landley.net/notes-2023.html>Rob Landley's Blog Thing for 2023</a><div>Oh good grief, two of my least favorite licensing people, Larry Rosen
 and Bradley Kuhn, are interacting on the OSI's license-discuss
 list where the're doing
 bad computer history and insisting that a guy Larry Rosen
-- 
cgit v1.2.3