Me: wipes cmos
My board: I've never met this ~~man~~ nvme in my life
this post was submitted on 12 Jun 2023
9 points (100.0% liked)
linux master race
83 readers
1 users here now
A magazine for Linux enthusiasts.
founded 1 year ago
Oh you wanted to make a small adjustment in your stable heavily modded game? Fuck you, spend the next six hours fixing it.
Who could have foreseen these consequences?
It's almost always /etc/fstab for me, thankfully.
Years ago I learned to always use vim when editing fstab for the syntax highlighting
Now you have to boot into USB, decrypt couple of hard drives, assemble raid, mount into place and chroot to start troubleshooting.
Iusearchbtw.
I feel you. Once I f’ed up my GRUB config file and I had to boot off an Arch USB to fix it. (Ialsousearchbtw)
Me: "Well I didn't really need it anyway, right?"
Oops, this happened to me after activating some systemd services years ago (forced me to boot into emergency mode to disable offending services)
It's fine, I wanted to try a different distro anyway...
When I was first getting into Ubuntu as a teenager I installed the grub bootloader on my dual boot install. I was shitting my pants when I restarted and it booted straight into Ubuntu instead of asking if I wanted Windows 7 or Ubuntu.
Guilty as charged. Also, mucking about with the Nvidia drivers for no good reason is also not a great idea, as I learned a few months back.
Broke my first Linux installation after just a couple month by mucking around with Nvidia drivers. And when I say mucking around, all I did was update them...
I've broken an embarrasingly large amount of Linux installs through mucking around with nvidia drivers.
Precisely why I bought an AMD card for my new rig.