Linux

1

Making errors and analysing them to figure out what went wrong and why is a huge part of learning. You can only learn so much from theory, some things can be learned best by trial and error and the experience gained from it.

When I started with Linux I did choose to use Gentoo Linux because it was the most complex and complicated option, so I had the most opportunities to learn something by ducking up!

Recently I accidently deleted the contents of /boot/ on my first arch install. The lesson that followed was something I would have rather saved for later ^^

I’m not sure I’ve ever actually killed a system, I’ve booted from UEFI shell manually just to recover systems. Back when I was using arch id just chroot into the system from a flash drive and fix whatever ¯\_(ツ)_/¯

.... So what should I try Linux again?

I haven't majorly fucked up any recent systems (almost botched the steam deck once or twice but nothing that required a reinstall), but god 10 years ago I probably reset my arch dual boot like five times lmao

I think we are using linux very differently. Mine is two and one of those was a dead ssd.

Two. The first time I had nvidia related issues with nobara, so I removed nvidia drivers for reinstallation... And couldn't figure out how to get them back. The second time I had used mint for long enough that I felt confident enough to nuke windows partition. I used gparted and nuked the whole disk instead.

Not counting the times I tried fedora and it killed itself with the first updates and then with multimedia codecs.

Unbootable systems in the dozens. I think I've only fucked up the kernel itself a few times. But grub or other bootloader tons, desktop environment tons, and getting into states so broken the only readily available option was reinstall, dozens. Thankfully most of these were right after a fresh install. For example dual booting just doesn't work right for some OS installers and grub fails. Manjaro bricked itself after an update. Etc. etc.

I started nearly 30 years ago and cannot count the dead systems I have left in my wake. Just on the 2000-ish thing where Dell first offered Linux but it was inherently unstable after booting the pre-written disk image if you touched it, alone... So many kernel sanity failures...

I remember managing to install two DE one above the other, and having them, somehow working at the exact same time. That was trippy.

I didn't even know how I did it. I'm pretty sure that I couldn't replicate that on purpose.

I'm on my second install now. I fucked up the first one pretty handily by accidentally wiping the boot partition in gparted. (Like a complete idiot, because the partitions are labeled.)

Both, to the point it doesn't boot, and just tweaking enough bugs that it's easier to jist start over.

I used to have a side system with /home on its own partition precisely to learn different distros and setups. It makes it much easier having a partition which is retained.

These days, qemu is your friend for playing around with random Linux stuff.

It do be like that, at least for the first couple years, and typically with decreasing frequency.

i broke debian on my plex server and said fuck it and migrated to endeavor because im more familiar with arch

I always think of Kiwi / Ozzie slang when I type chroot.

Of course that's after consulting the ArchKiwi to remember how to mount it