My crippled kernel count is around 6, how about yours?
Not any moreso than learning any other OS. I’d just argue that it’s the case if you’re averse to research, reading, listening, watching, or just generally learning from others… or if you’re delving into unknown territory
Personally, i’m a learn-by-doing type of lady, so I’ve fucked up my share of devices (I’m allergic to reading unless it’s fiction), but I have yet to mess around in the kernel (it’s on my todo list, for my LFS build which is TBD)
Nearly always it’s been during the live USB install of a dual-boot that a distro messes with the grub or installed grub to the USB disk itself. The fault lies with me because I’m almost blindly trusting the distro, but also with the distro for lacking proper yet succinct documentation during the install or configuration of partitions.
I just spent 11 days on a dual boot repair in fstab, passwd, loads of ecryptfs, amongst other boot and login issues. Before restoring from the full system backup after getting mad to finally want to use my PC. 11 fucking days almost all day in terminal. TOO many partitions and too many folders inside of folders to get to my ecryptfs files. I got so lost LSing around.
After it all though, and it was an aneurism and a half. I still want to finish my goal and reinstall my dual boot this time correctly aiming the folders correctly.
No no no! When you break something in Linux systems you fix it. Starting over and reinstalling everything is what you do when you mess up on Windows.
Generally yes. My exception was the time i accidentally nuked python in it’s entirety…
Well, that could have been fixed by booting from an usb stick, chrooting into you real system and either downloading and (re)installing the python package this way, or, if your package manager depends on python, download the package in the Live Linux and extracting the python package into your system, and then reinstalling it, so the package management overwrites your “manual installation”.
Could be tedious, but less so that having to reinstall everything IMO.
Funny I did not expect so many people that resist starting over. Next time I’ll give fixing stuff a shot :)
It is more about being lazy.
In most cases, where you havn’t destroyed your filesystem, you can just boot another Linux from a USB stick, mount your filesystems to /mnt, chroot into it, and then investigate and fix there.
See the Archlinux wiki, even if you do not use Archlinux, it is great: https://wiki.archlinux.org/title/Chroot
I would actually be amazed if I ever bricked a PC fucking around with installing software to it. At the very worst, I might have to move a jumper pin to flash the CMOS and start fresh like I never even touched the thing. If somehow even that fails, it would be a unique experience.
