As far as backups go, I prefer the fire-and-forget method where you just image the entire drive and dig into it when you actually need something. Using separate

As far as backups go, I prefer the fire-and-forget method where you just image the entire drive and dig into it when you actually need something. Using separate drives for root and home makes it easier. Backup to backblaze to fulfill 3-2-1. Storage is just so cheap it's not worth the effort to try to get it efficient. I also find its not worth the effort to migrate bookmarks and stuff (I just rarely revisit them) and use a NAS for the bigger stuff like pirated media. 1password and Firefox sync take care of everything else. I usually restore dot files and other home directory stuff from Git using the procedure described in this HN thread: https://news.ycombinator.com/item?id=11071754 https://news.ycombinator.com/item?id=11071754 Dev environments are predominantly implemented using nix, flakes, and direnv on a per project basis so there's no migration there. I've got a few scripts that dump a list of major packages installed on my ArchLinux system so I can reinstall them in bulk instead of chasing them down one by one afterwards. Another script to go through the file system and delete all the rust target folders, node's node_modules, etc. and a list of caches (yarn, docker, etc.) I keep the data forever as a hoarder since drives are so cheap but I very rarely have to look through them. Never even heard of LogoFail. I guess their exploit name wasn't catchy enough to grab my attention