I take the somewhat unusual approach, Of hosting this Web-site, and therefore also my blog, on my personal computer at home. Therefore, any downtime of my home computer, also affects the visibility of the blog. And, as long as the actual Web-server is not online, I also cannot make it display a maintenance-mode page.
Just in recent days, I took the more-unusual step, of running the command:
root@Phoenix:/home/dirk# update-initramfs -u -k 3.18.0-14-generic
What was unusual about this, was the fact that this was not the command:
root@Phoenix:/home/dirk# update-initramfs -u -k 3.16.0-4-amd64
While it seemed nice for some time, to be running a kernel-version named ‘3.18.0-14-generic’, the mainstream version which a Debian / Jessie system is supposed to be running, is ‘3.16.0-4-amd64′. So, while the mainstream kernel had been receiving regular updates, I was running a kernel, which had not been receiving any updates, for years now. This helped reduce the number of reboots which I needed to carry out, due to frequent updates on the ‘3.16.0’ kernel.
But just because this was the first time in ages, that I had run the ‘update-initramfs’ command on the running kernel, I next needed to attempt a reboot, just to see whether the computer could still boot.
Therefore, readers would have experienced problems accessing my blog or site, from about 16h40 until about 17h10 today.
And No, My system Failed to Reboot.