I don’t nas, but I suggest a combination of offline drives, cloud services or remote hosts, and just ignoring data that is easy to recreate like builds and software installs.
The key is to keep the data organized in such a way that you know which parts deserve which strategy.
On one hand it’s a risk that there would just be some terrible version that ruins all public things connected with the name, but on the other hand there could be something fantastic.
I guess sandman is already off the list. Haven’t seen the results though.
Another big risk in adaptations is that, like Peter Jackson’s Lott, it will make it very unlikely that someone else would come up and do it better after a big enough attempt.
Me too. I’ve run 30 years with ext and bsd filesystems with no failure. Many years with various UNIX native fs as well. But Linux xfs, reiserfs, btrfs all have resulted in catastrophic failure within a year on several machines. They’re permanently off my list, but I have some hope that someone will get a new fs right.
I really hope it would be a working one, not like xfs where your files may just disappear with no trace (never on Irix, never on any other fs) or like btrfs which may just suddenly go read only and be dead on reboot with no fsck and all data unreachable.
How hard is it to get the basics right? Doesn’t matter how much rice there is if it keeps blowing up.
It does take some time to get going and a few stories are pretty dense. But it’s also a good re-read, especially after reading some notes about the things you missed the first time around. There’s a crazy amount of detail and characters.
www.iloq.com for example does a lot of parasitic energy stuff. Most of the advertised things now seem to be RFID, but I think they also had locks that are powered by the key insertion.
There’s plenty of places where infrastructure power is not available and a flat battery would be a disaster. Door lock is one mundane one. Space is one more extreme one.