Arch is good for tinkering with to make it your own, but can sometimes require tinkering to do things other distros can do straight away, e.g. adding udev rules to use certain devices or setting up zeroconf to be able to discover printers on the network automatically

If you want to be able to roll back changes easily you could set up your root and home partitions as btrfs subvolumes and use snapper to take snapshots, which can be combined with pacman hooks to automatically take snapshots when updating/installing software and can even be set up to allow booting into the snapshots which could be useful if you break your system

Yeah, I think this is likely what happened, will be interesting to see what the investigation finds. I’m surprised there isn’t any sort of backup power for the voice recorder, it’s there to help investigate incidents, those 4 minutes would have contained a lot of vital insight into what was going on.

Runways can be used from either direction, usually they try to land with a headwind if there is significant wind I think. I think the localizer antenna can be at both ends of the runway if both directions have ILS approaches, but I’m not an expert. The concrete mound for the antenna is getting a lot of focus because it made a runway excursion so much worse.

It seems to me like they may have decided to make the landing then due to losing altitude and thinking they wouldn’t be able to climb again, but hopefully the investigation can figure out what probably happened.

If you’re using BTRFS and know how to/are prepared to learn, just create separate sub volumes instead of multiple partitions. Means that you don’t need to decide how to split up space between different partitions and they are easy to delete without a live USB.

deleted by creator