1 files changed, 9 insertions, 1 deletions
diff --git a/posts/2021-12-15-rescuing-freebsd-the-unix-way.php b/posts/2021-12-15-rescuing-freebsd-the-unix-way.php
index 1b54d63..cec623d 100644
--- a/posts/2021-12-15-rescuing-freebsd-the-unix-way.php
+++ b/posts/2021-12-15-rescuing-freebsd-the-unix-way.php
@@ -60,7 +60,7 @@
 </pre>
 
 <p>
-	It took literally half the day. Poor little dual-core i5. It was already well on its way to completing when I realized I could have done this on my 8-core/16-thread server. "Oh, so you're reckless <em>and</em> stupid." Don't worry, I redeem myself later. Now I can actually install the new kernel and reboot into it. This is required before installing the world (userland).
+	It took literally half the day. Poor little dual-core i5. It was already well on its way to completing when I realized I could have done this on my 8-core/16-thread server<sup><a href="#1">[1]</a></sup>. "Oh, so you're reckless <em>and</em> stupid." Don't worry, I redeem myself later. Now I can actually install the new kernel and reboot into it. This is required before installing the world (userland).
 </p>
 
 <pre>
@@ -167,3 +167,11 @@
 <p>
 	Redemption. I went from attempting to customize my kernel to annihilating <code>/usr</code> to restoring my entire system by building from FreeBSD's source tree via <code>git(1)</code> and <code>make(1)</code>. And I got a free upgrade out of it! Moving forward, I'm running slightly frequent automatic full-system snapshots. It should make it a lot easier to rescue accidental deletions of system files. I'm also going to take the time to learn more about the rescue disk process using the FreeBSD installer image. All told, not too bad for a disaster-turned-learning-experience.
 </p>
+
+<hr>
+
+<ol>
+	<li id="1">
+		I actually did move my FreeBSD source to my server to let it pull changes and do automatic builds. Turns out it can chunk out the whole world and kernel in about TODO:
+	</li>
+</ol>