I’m not familiar with Arch’s updating scheme, but I’d bet that it’s pretty similar to Red Hat’s and Debian’s. If you don’t complete an update, boot it up — even if it’s in a semi-broken state — and just start the update again. Even if the thing dies right in the middle of updating something boot-critical, so that it can’t boot, you can probably just use liveboot media, mount the drives in question, start a chrooted-to-your-regular-root-partition root shell, and restart the update.
Doing that and installing or reinstalling packages is a pretty potent tool to fix a system. It’s not absolutely impossible that you can manage to hork a system up badly enough to render it still unusable in that situation — I once wiped ld.so from a system, for example, and had to grab another copy and manually put it in place to get stuff dynamically-linked stuff like the package manager working again. But that’ll deal with the great majority of problems you could create.
I’ve done this countless times. My case was weird since I had a monitor that managed to regularly destroy my system but the gist is the same.
Got to a point where I put a text file on my live stick to copy-paste the commands to untangle the clusterfuck. Could probably format it to a bash script but I’m lazy ¯\(ツ)/¯
if i had any money i would donate it instead of just lighting a candle
Tbh arch is very resilient and easy to fix
Linux god’s
Linux god’s what?
kernels
