Ok, just went through a bit of a right of passage I'd somehow doged until now: my WM hard crashed durring an #arch update, leaving me with an unbootable kernel.
A few hours (and a few boots to a live USB) later, and I'm back in and have restored the damage with no data lost. But it's (another!) wake up call that I need to be better about backing things up (and maybe find a WM that doesn't crash…)
And yes, #guix folks, I know this wouldn't have been an issue with your distro :D
> I use #arch on ZFS. Used to use Btrfs. Both support boot environments and snapshots. Everytime you update the system you can take a snapshot and setup a boot environment. If the update fails you just boot from the snapshot from you bootloader (ie. Grub, reFind, Systemd-boot, etc)
Yeah, setting up #ZFS is on my to-do list, but hasn't been a priority. Maybe this will inspire me to actually get around to it
@codesections
I use #arch on ZFS. Used to use Btrfs. Both support boot environments and snapshots. Everytime you update the system you can take a snapshot and setup a boot environment. If the update fails you just boot from the snapshot from you bootloader (ie. Grub, reFind, Systemd-boot, etc)
Btrfs is easier to setup since it's baked into Linux. ZFS was more work, but I really like how it works and it is more reliable.