added some blog thumbnails and some small fixes

3 files changed, 53 insertions, 20 deletions

diff --git a/content/blog/a-nas-tale.md b/content/blog/a-nas-tale.md
index ba39bb5..661e691 100644
--- a/content/blog/a-nas-tale.md
+++ b/content/blog/a-nas-tale.md
@@ -2,22 +2,53 @@
 title = "A NAS tale"
 date = "2017-01-21T14:10:11+01:00"
 categories = [ "Hardware", "NAS", "Linux" ]
+thumbnail = "/images/blog/a-nas-tale/a-nas-tale.png"
 +++
 
-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…
+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/openbsd-firewall-and-securityrouter.org.md b/content/blog/openbsd-firewall-and-securityrouter.org.md
index 13a800e..178b827 100644
--- a/content/blog/openbsd-firewall-and-securityrouter.org.md
+++ b/content/blog/openbsd-firewall-and-securityrouter.org.md
@@ -2,6 +2,7 @@
 title = "OpenBSD firewall and securityrouter.org"
 date = "2017-01-08T12:01:22+01:00"
 categories = [ "OpenBSD", "Security" ]
+thumbnail = "/images/blog/openbsd-firewall-and-securityrouter/openbsd-firewall-and-securityrouter.png"
 +++
 
 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.
diff --git a/content/blog/statig-gen-hugo.md b/content/blog/statig-gen-hugo.md
index ea1e442..7dec9ed 100644
--- a/content/blog/statig-gen-hugo.md
+++ b/content/blog/statig-gen-hugo.md
@@ -3,13 +3,14 @@ date = "2017-02-12T16:03:44+01:00"
 description = "Static HTML generators"
 title = "Website done with StaticGen Hugo"
 categories = [ "Web", "HTML", "Go", "Hugo" ]
+thumbnail = "/images/blog/statig-gen-hugo/statig-gen-hugo.png"
 +++
 
 Some years ago I decided to write my personal web page as a bunch of
 static HTML pages using only server-side includes to cope with the
 repetitive elements like footer, header, menus. When I installed a
-Wordpress just for the blog I intended to start I thought: why can't
-this be done statically too.
+Wordpress just for the blog I intended to start, I thought: why can't
+this be done statically too?
 
 In fact, it can be done: the following web pages show an explosion 
 of tools for static HTML site generation:
@@ -21,7 +22,7 @@ I decided to go with [Hugo](https://gohugo.io/). The model is quite
 simple if you get your head around it. It has live reloading in the
 browser when you save the Markdown (or actually any file) in the text
 editor. It's written in Go, so I don't have to worry about 10'000
-Ruby, Javascript, Perl, Python packages getting installed and break
+Ruby, Javascript, Perl, Python packages getting installed and breaking
 all the time. Go packs everything into static binary and is blazingly
 fast. The idea with sections and types which can be templated, it is
 powerful enough to produce a site like mine. Even having an alternative