Kernel Update Yesterday, Downtime

I use the uncommon methodology of hosting my site, and this blog, on a home computer. And this means that the reliability with which my Web-pages can be fetched, is only as good as the reliability of this home computer, which I name ‘Phoenix’. I don’t necessarily recommend that other people do this; this is just how I do it.

Yesterday (05/08/2018) , the Debian maintainers pushed through another kernel update. After a kernel update, even a Linux computer needs to be rebooted. And the result from that would have been, that my site and blog would not have been accessible to the Internet, from about 19h55 until 20h05.

The last kernel update only took place recently.

I’m sorry for any inconvenience this may have caused my readers.

The kernel update itself seems to have been uneventful on any level that I was able to observe.



Kernel Updates Today, Downtime – VirtualBox Maybe Affected

I take the unusual approach, of hosting my Web-site, and this blog, on my personal computer at home. This implies that the visibility of this blog on the Web, is only as good the reliability of my PC, which I name ‘Phoenix’. Along with the computer I name ‘Plato’, Phoenix received a kernel-update today, which required a reboot.

The kernel-update took place uneventfully.

But, my site and blog would not have remained visible, from 20h20 until about 20h30 this evening.

I apologize for any inconvenience to my readers.

(Update 05/02/2018 … )

Contrarily to first appearances, this kernel-update did seem to have a side-effect: On one of my computers, it prevented the VirtualBox kernel-modules from being built…

Continue reading Kernel Updates Today, Downtime – VirtualBox Maybe Affected

Kernel Update Today, Downtime

A fact about mys site which some people may not know, is that I take the unusual approach of hosting it on one of my PCs at home. The computer which acts as my Web-server, is also the one I named ‘Phoenix’, and which is still running Debian / Jessie. What this piece of trivia means in practice, is that any downtime of this one PC, also causes the site not to be accessible on the Internet. This is very different from how it would be, if I was to pay a professional hosting service.

Today, ‘Phoenix’ received a long-awaited kernel update, With which the package maintainers hope to be mitigating the ‘Meltdown’ vulnerability. What this does, is complete the work that some of the System Programmers have been doing, on the ‘Meltdown’ vulnerability, since as it stands, all the kernels on the list here have been patched now.

The fact is somewhat ironic, that ‘Phoenix’ has an AMD processor, and was therefore never directly susceptible to this form of attack. However, the computer which I name ‘Plato’ has an Intel CPU, and received its kernel update on January 5.

I congratulate the kernel-programmers on a milestone in their work.

Now an unanswered question remains, as to what will be done – if anything – about ‘Spectre’, which is a related vulnerability, in which a hypothetical attacker would ‘attack’ other processes running on the same machine, but not the kernel. The problem with ‘Spectre’, as far as I think I understand it, is that it involves “Speculative Execution” of code, but does not involve ‘system calls’ per se. What that means is that, unless somebody comes up with something brilliant, the only ways to patch that would either be to disable Speculative Execution entirely, or, switch to new chips, which have been designed with ‘Spectre’ taken into account, but which haven’t been designed yet in fact.

‘Spectre’ may also affect some AMD CPUs.

In any case, my site was unavailable from about 15h30 until 15h45.



Routine Kernel Update Today, Downtime

I host this site on a Debian / Jessie (Linux) computer, which I name ‘Phoenix’. Through the package manager, it receives routine kernel updates, and today was a day on which it received one.

Even on a Linux computer, a kernel update generally requires a reboot, which I carried out.

But, because This computer is also my Web-server, and the host to my blog, that means that for a few minutes my site and blog were offline – i.e., unavailable to readers. This was happening from approximately 19h45 until 19h55.

I apologize for any inconvenience.

For what it’s worth, I consider this to have been one of the least-troublesome reboots, that I’ve had to carry out over the years.