summaryrefslogtreecommitdiff
path: root/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.html
diff options
context:
space:
mode:
Diffstat (limited to 'gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.html')
-rw-r--r--gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.html b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.html
index e605a60f..42c3e924 100644
--- a/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.html
+++ b/gemfeed/2016-04-09-jails-and-zfs-on-freebsd-with-puppet.html
@@ -90,7 +90,7 @@ p.quote:after {
\ `. hjw
\ `.
</pre>
-<p class="quote"><i>Written by Paul Buetow 2016-04-09</i></p>
+<p class="quote"><i>Published by Paul Buetow 2016-04-09</i></p>
<p>Over the last couple of years I wrote quite a few Puppet modules in order to manage my personal server infrastructure. One of them manages FreeBSD Jails and another one ZFS file systems. I thought I would give a brief overview in how it looks and feels.</p>
<h2>ZFS</h2>
<p>The ZFS module is a pretty basic one. It does not manage ZFS pools yet as I am not creating them often enough which would justify implementing an automation. But let's see how we can create a ZFS file system (on an already given ZFS pool named ztank):</p>