changed website and blog to use Hugo

4 files changed, 37 insertions, 0 deletions

diff --git a/content/blog/_index.md b/content/blog/_index.md
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/content/blog/_index.md
diff --git a/content/blog/a-nas-tale.md b/content/blog/a-nas-tale.md
new file mode 100644
index 0000000..25a7600
--- /dev/null
+++ b/content/blog/a-nas-tale.md
@@ -0,0 +1,22 @@
++++
+title = "A NAS tale"
+date = "2017-01-21T14:10:11+01:00"
++++
+
+In August 2009 I decided it was time to replace my old Pentium II serving 5 old SUN storage disks (the white boxes, enormously noisy, for those who remember) with a modern NAS system. I bought a QNAP TS-439 Pro. The integrated firmware (aka customized Linux) gave me the creeps from a software design point of view, but it did the job.
+
+Almost exactly a year later there was a fatal event and my software RAID (RAID 5) decided not to assemble anymore. I thought, well, the hardware is pretty standard, why not give Centos a try. Worked well till…
+
+After two and a half years there was Centos 5.9. It introduced a fatal NFS bug which made you see only half of your data (something with caching of inodes). So I turned my back on Centos (on the NAS, not otherwise).
+
+In 2013 I finally installed Archlinux (after a rather disastrous experience with Ubuntu 12.04 LTS). Ubuntu was not happy with the 1 GB of RAM and NFS just performed poorly.
+
+After 4 years I can say, there is nothing wrong with having a bleeding edge Linux distribution like Arch Linux on a NAS. I can recommend using the LTS kernel though as you may end up in trouble with the bleeding edge one from time to time.
+
+In summer 2015 I had the brilliant idea to move the now a little bit noisy NAS into a cabinet under a hot tin roof (sounds stupid, right?). Of course, the PSU went belly up, the DOM (small flash drive to boot via an HDA connector) melted. The PSU model (PSU FSP220-60LE) was a little bit tricky to get and the replacement DOM was just about 2 millimeters too high and needed a good squeeze to fit into the case. The layout in the box is quite cramped (it’s very small and cubic in the end), and I was really happy I didn’t have to replace the motherboard.
+
+The real issue was a sector bug on the software RAID. This is a case software RAID usually doesn’t handle well and where you are better off with a hardware RAID. I had to ‘dd’ the block data manually and reallocate sectors on the disks.
+
+Another real problem is having only 1 GB of RAM. Seems ‘fsck’ on 4 TB data uses just a little bit too many data structures in memory to be able to check the whole filesystem. There is a mode of fsck, which works with small temporary files on disk instead of in memory, but it’s very slow and besides, who wants to check a filesystem storing temporary files on the same physical disks as where he is doing the fsck on?
+
+Since then, no more incidents occurred and the machine is working reliably, though the fan is a little bit noisy and could do with a little bit of cleaning…
diff --git a/content/blog/intro.md b/content/blog/intro.md
new file mode 100644
index 0000000..c8ba225
--- /dev/null
+++ b/content/blog/intro.md
@@ -0,0 +1,8 @@
++++
+title = "Mission Statement"
+date = "2017-01-05T10:00:37+01:00"
++++
+
+This is a personal blog. I intend to post on technologies and ideas currently in my mind.
+
+Take everything I write with a grain of salt.. ;-)
diff --git a/content/blog/openbsd-firewall-and-securityrouter.org.md b/content/blog/openbsd-firewall-and-securityrouter.org.md
new file mode 100644
index 0000000..27f34d0
--- /dev/null
+++ b/content/blog/openbsd-firewall-and-securityrouter.org.md
@@ -0,0 +1,7 @@
++++
+title = "OpenBSD firewall and securityrouter.org"
+date = "2017-01-08T12:01:22+01:00"
++++
+
+Found a really nice new router appliance based on OpenBSD 6.0, http://securityrouter.org. I’m still missing some features like a split-horizon DNS, so I will not abandon the script-based project http://github.com/andreasbaumann/OpenBSD-firewall just for now.
+