Comment by aamederen
For a more baby-steps approach to resiliency, one might start running software on less-virtualized computers, creating a small home-lab, running software on bare-metal hardware that you actually own.
For a more baby-steps approach to resiliency, one might start running software on less-virtualized computers, creating a small home-lab, running software on bare-metal hardware that you actually own.
Many people already do that (e.g. I use Linux on a Laptop- I consider this bare-metal).
The way I read this, it's more about what is needed to get services back up after a large scale loss of critical infrastructure: communication to other network/internet/infrastructure professionals.
Or even just install local software. Get a computer that lasts (have at least one non laptop). Have maybe some maps and Wikipedia locally.
Maybe walkie talkies too? Pretty simple to use!
I spent the weekend moving all my personal projects away from github & AWS to to dedicated hardware in the EU, still not in my own home, but I'm toying with the idea of purchasing some hardware to run gitlab etc from my home network.
Renting dedicated hardware is expensive though. I'm taking a financial hit for my paranoia.
I host many services from a small rack in my home using FreeBSD jails.
Also related though maybe not resiliency-focused: It's quite easy now to download all of Wikipedia and all of Project Gutenberg to a hard drive, so that whatever problems you have in the post-apocalyptic hellscape, boredom won't be one of them.
Kiwix is the best software I have found for this and they make an extensive library of materials available for download themselves, which includes the aforementioned but also many other resources that would be helpful in a disaster scenario: https://library.kiwix.org/