this post was submitted on 04 Sep 2026
88 points (85.5% liked)
Linux
67647 readers
394 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 7 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've been using Arch since 2008 or 2010, idk. I find it easy and intuitive but I still managed to fuck it up multiple times by now. All of those major fuckups I can remember could probably have been solved by what you're trying to do with Pu-239.
List of major fuckups off the top of my head, chronologically:
Once it had suddenly contracted some kind of computer AIDS which made the windows pink and caused other graphical errors. Never figured out why, a reinstall solved it.
Another time I installed a bunch of packages without doing a full repo sync before (
pacman -Sinstead of-Syu), which left the system in an inconsistent state. Had snapshots of the root partition I could roll back to.The third time happened only recently and made my desktop unusable for half a year because I couldn't be bothered to fix the fucking bootloader. Huge update (4-5GiB in size, didn't update for a few weeks or months even) slowed down the whole system due to btrfs having some exhausted inodes or sth, which made the system crash and the bootloader disappear. This even fucked up my firmware so for whatever reason the system can't boot from /boot, only from the EFI system partition. My current workaround is copying the files from /boot to the ESP until I can be arsed to figure out the issue.
Damn that sounds like a pain in the ass. Yeah, I personally have btrfs snapshots set up on my main workstation and had to use them once, but I just envision having peace of mind that you won't even noticing that something broke.
Exactly why I found your idea very cool :)
With Multi-Kernel Linux you could even try booting it before you try booting it, haha 😄