edit: for anyone curious, the problem was Xorg wasnt loading or something (stuck on systemd 'graphical interface target reached' with no graphical interface). because of a typo in a config file.
literally about to do this today. Ubuntu->Fedora
I guess the "small bug" is that you have microsoft windows on the drive for dual booting. Otherwise I wouldn't know what sort of bug you'd get rid of like this.
I recently fucked a system because I wanted to resize the swap partition. Started throwing time after trying to recover. Realized that even if I succeeded, I'd have spent more time recovering than it would take to reestablish a new system, and no important data was on the system.
I have some Linux servers in hyper v virtual machines and i just revert then to a previous snapshot if I mess anything up instead of bothering with diagnosing what I did 🙃
Haven't needed to do either yet since I started using #EndeavourOS. I'm a bit surprised, given how many posts I've seen about people bricking their Arch installs.
People who use arch tend to wonder how other people manage to break arch so hard and often. At least that's been my experience since I started using arch.
Yeah I've been on it a solid 5-6 months and the only issue I had was on initial setup I forgot NetworkManager or lost it somehow. That was literally the only issue. Been less issues than Windows since.
I mean I've had no end of problems, generally created and fixed by me. But none of them have raised to the level of breaking my machine or operating system. I guess I did upset it by giving fstab bad info, but it's not like I managed to uninstall system packages or something.
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!