A big part of learning Linux is screwing up computers and starting over.
A big part of learning Linux is screwing up computers and starting over.
My crippled kernel count is around 6, how about yours?
A big part of learning Linux is screwing up computers and starting over.
My crippled kernel count is around 6, how about yours?
You're viewing a single thread.
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.
Fair, unfortunately it was a work machine that i needed operational again asap.
Luckily i image my machine monthly, so it was fairly straightforward to roll back.
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