Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
Jumping from the default kernel with zfs to the xanmod kernel using a manually compiled version of zfs. I don't rememeber a whole lot but it was quite... interesting. Next would be a suddenly vanished efi partition and my f* mainboard refusing to boot ZBM.
Bonus: my currently still unfixed problem is a very weird freezing/stuttering of the whole OS and the only (useless) "lead" I have is workqueue: fill_page_cache_func hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND
Used to be messing with kernel arguments and installing/tweaking boot parameters. That was until Grub broke, I learned systemd-boot and chrooting into the system via live USB
Now if I break anything it's just a matter of "sigh, let me get the USB and type a few commands"
Fast data transmission via TCP over a lossy link.
I recently managed to recover from a corrupted libstdc .so. Turns out I shouldn't have bothered because the it was a Pi and, of course, the SD card had shit the bed, but I was pretty happy with myself for like 30 minutes.
Installed fedora on btrfs and upgraded from 38 to 39 week after installation, everything broke so bad, even ssd which was used for it locked, not just filesystem, ssd was new btw
I don't know how I fixed it, but KDE Plasma 5.whatever on MX was acting up. It would let me login but if I couldn't do much else. Wouldn't respond to my clicks or anything. Thankfully I could open Yakuake and install a different desktop environment. Then, one day while I was backing up files to do a reinstall, it started working again. I could use Plasma without issues. I have no clue what fixed it, though.
It also came with a non-issue of now my laptop won't auto turn on every time I open it up, but I'll take that over having to reinstall and set things back up.
My first home server would get lost on the network every week, at different times and without any apparent reason. I performed hard resets by unplugging and plugging it back in.
After several months, I decided to connect a screen to it, and I initially thought it had hung up, but it hadn't. After some investigation, I discovered that every time my router obtained a new dynamic IP address, the server lost its network connection, requiring a reset. I wrote a script to check the network connection every minute, and if it's lost again, it will be reset.
Some of the crap I had to do back in the late 00s to get wifi, sleep and power management even barely working on some machines felt like the hardest thing at the time. I wonder how I’d fare with those issues today, 17 years later, knowing quite a bit more about the underlying OS and working with the OS daily… I don’t know that I’d qualify that as difficult more than it was extremely tedious and a bunch of trial and error of configuration options I didn’t know anything about.
If we’re talking about modern day… not so much honestly. btrfs snapshots saved my ass a couple of times, the rare issue I encounter I just rollback and wait for an upstream fix, and the rest I typically ignore or use something else. Everything tends to run quite smooth for me as a general rule, though.