# Linux recovery adventure and more
I had to recover from a broken Linux kernel today. I had installed a
new version of the kernel, missed the out-of-disk message,
reconfigured to use the new kernel and purged all the older kernels.
The result was grub being configured to boot from a corrupt kernel
image, and no other images in the menu.
From that I ended up not being able to boot, no surprise there. I
downloaded a live image for my distribution. Having booted into it I
mounted my rootfs and the dev, proc, tmp and sys within and
chrooted. From there I could run the regular commands to redownload
and reconfigure the kernel. It booted!
This is probably routine to some, but when I last had an issue like
this some 10 years ago it seemed catastrophic. This time I only
occasionally had to refer to manual pages. So I have learned a lot
since then, I think, which is always a good feeling. What I learned
now is that it's good to keep a recovery disk available, review the
system update logs and to always keep a known-good kernel while
purging other kernels to leave some space on the boot partition.
In other news I started at a new position at a client this week,
writing Go code for an embedded network system. I've been writing
that was fun for a while, the novelty wore off towards the end. As a
prevalence on websites that really don't need it is a shame. The new
assignment is much more in line with how I think software should be