tNew article ! - monochromatic - monochromatic blog: http://blog.z3bra.org
 (HTM) git clone git://z3bra.org/monochromatic
 (DIR) Log
 (DIR) Files
 (DIR) Refs
       ---
 (DIR) commit c7b002d679d4df9fdc8f38828e766b48e168fe59
 (DIR) parent f1875c63f7c97dd29714e2f9a97a779c15e6df38
 (HTM) Author: z3bra <willy@mailoo.org>
       Date:   Tue, 19 Aug 2014 09:37:57 +0200
       
       New article !
       
       Diffstat:
         A 2014/08/im-back-up.txt              |      84 +++++++++++++++++++++++++++++++
         M config.mk                           |       7 +++++--
         M index.txt                           |      14 ++++++++++++++
       
       3 files changed, 103 insertions(+), 2 deletions(-)
       ---
 (DIR) diff --git a/2014/08/im-back-up.txt b/2014/08/im-back-up.txt
       t@@ -0,0 +1,84 @@
       +# [I'm back up !](#)
       +## &mdash; 05 August, 2014
       +
       +In the past few days, my whole server (and thus, my website) was down.
       +
       +Everything is now back to it's normal state, so I'll give you a quick
       +explanation about what happened.
       +
       +### TL;DR
       +Quickly, here's what happenned (the whole process took approximately 2 weeks):
       +
       +1. Changed distribution
       +2. Changed hardware
       +3. Realised new hardware is broken
       +4. Bought new hard drive
       +5. Fallback to old hardware
       +6. Reinstalled distribution
       +
       +### I'm sorry
       +As you can imagine, I did not plan such a long downtime. It was, at first, only
       +a matter of 2 or 3 days, but ended up being almost 2 weeks. So first of all,
       +please accept my apologizes.
       +
       +### The situation
       +Now, let me tell you what happened. Some relatives gave me an old PC they were
       +not using anymore. It had a dual core and 2GB of RAM !!
       +
       +So I decided it was time for my old server to retire a bit, and by the time, to
       +change the distribution powering it. I settled on
       +[alpinelinux](http://alpinelinux.org), a fairly light and fast distribution
       +powered by musl libc and busybox.
       +
       +The install went fine and I brought the server online again. And then, it
       +began...
       +
       +### The problem
       +    ─── ssh z3bra.org
       +
       +             __   __
       +           /'__`\/\ \
       +     ____ /\_\L\ \ \ \____  _ __   __
       +    /\_ ,`\/_/_\_<\ \ '__`\/\`'__/'__`\
       +    \/_/  /_/\ \L\ \ \ \L\ \ \ \/\ \L\.\_
       +      /\____\ \____/\ \_,__/\ \_\ \__/.\_\
       +      \/____/\/___/  \/___/  \/_/\/__/\/_/
       +
       +                            -- silly, isn't it ?
       +
       +    Enter passphrase for key '/home/z3bra/.ssh/z3bra.org':
       +    ─ g ── cd ~/src/www/monochromatic
       +    ─ g ── vim last.txt
       +    ─ g ── make
       +    /bin/sh: /usr/bin/markdown: I/O error
       +
       +*OooOh god, what happened...?*
       +
       +I'd better shut it off before it goes bad...
       +
       +    ─ g ── sudo poweroff
       +    /bin/sh: /usr/bin/sudo: I/O error
       +    ─ g ── su -c poweroff
       +    /bin/sh: /usr/bin/su: I/O error
       +
       +.. Too late ...
       +
       +By the time, I was not sure wether the problem came from the hard drive itself,
       +or the whole mother board.  
       +I decided to boot the drive from my old server, and I did not have any problem
       +from it. Looks like I could only rely on my good ol' hardware.
       +
       +### The solution
       +
       +I finally decided to buy a new hard drive, and to run it from my old
       +hardware. The motherboard of the "*new*" one was on the end of its life,
       +and having all my data on an USB external drive was a bit of a pain in the neck.
       +It boots slowly, and if I'm not careful, I can just kick it and loose all my
       +datas.
       +
       +I finally reinstalled alpine on the new hard drive, and finally brought the
       +server back up !
       +
       +It feels good to be online !
       +
       +<!-- vim: set ft=markdown ts=4 et tw=80: -->
 (DIR) diff --git a/config.mk b/config.mk
       t@@ -1,7 +1,7 @@
        MD      =/usr/bin/markdown
        
        NAME    = monochromatic
       -PREFIX  = /srv/http/blog.z3bra.org
       +PREFIX  = /var/www/http/blog.z3bra.org
        
        PAGES   =   index.html \
                    about.html \
       t@@ -15,7 +15,10 @@ PAGES   =   index.html \
                    2014/03/toolbox.html \
                    2014/04/meeting-at-the-bar.html \
                    2014/04/pop-it-up.html \
       -            2014/05/grok-that-workflow.html
       +            2014/05/grok-that-workflow.html \
       +            2014/07/planning-downtime.html \
       +            2014/07/name-that-domain.html \
       +            2014/08/im-back-up.html
        
        FEEDS = rss/feed.xml
        EXTRA = css img vid errors favicon.ico
 (DIR) diff --git a/index.txt b/index.txt
       t@@ -1,3 +1,17 @@
       +# [I'm back up !](/2014/08/im-back-up.html)
       +## &mdash; 05 August, 2014
       +... And I'm sorry about the inconvenience. Here's the reason of the downtime.
       +
       +# [Name that domain](/2014/07/name-that-domain.html)
       +## &mdash; 10 July, 2014
       +I finally dropped the heavy `BIND` for a much lighter solution.
       +Here is a tutorial on how to set up `tinydns` and `dnscache` to act as a DNS for
       +your local network.
       +
       +# [Planning downtime](/2014/07/planning-downtime.html)
       +## &mdash; 02 July, 2014
       +I will upgrade my hardware in a few days, and change the distribution that powers my server in the mean time. See you when I'm back up !
       +
        # [Grok that workflow](/2014/05/grok-that-workflow.html)
        ## &mdash; 30 May, 2014
        In a pretty narcissic pulsion, I decided that it could be interesting to