Linux is slow at killing apps when you run out of memory because it was designed to also run on low spec hardware even if very slowly (making the ui totally unrensposnive) due to swapping.

This comic is about the kill command, how Linux kernel is handling force stopping apps vs (old?) Windows when if App frozed it was hard to close it. Now with modern apps and hardware you very rarely see that as most apps are designed to have asynchronous logic that is correctly handled, but it’s still more or less relevant.

No Arch? Strange…

You can use (self hosted) gitlab as a registry storage. We do that locally so we have both code, pipeline and containers in the same place.

For VR, if you have a Quest headset and good WiFi, you can try ALVR with SteamVR, it works just fine for me while playing BeatSaber but depending on games your milage might vary.

But you have a lot of cold air to cool it down, and on a side note it makes your room warmer which you might want in that cold region 😅

(But the energy savings is hard to argue with)

Just having btrfs is not enough, you need to have automatic snapshots (or do them manually) before doing updates and configured grub to allow you to rollback.

Personally, I’m to lazy to configure stuff like that, I rather just pick my Vetroy USB from backpack, boot into live image and just fix it (while learning something/new interesting) than spend time preventing something that might never happen to me :)

Old good factorio headless Penguin, it’s like that for so long…

Hello fellow Factorio players :)