Once you get it all setup and proud of your work, make a fucking backup image, because a single update that changes an obscure library in some forgettable package that was part of your install will break everything and you will be pulling your hair out kludging a CLI script to unfuck some other binary that was unimportant, but now has affected another thing that was crucial for a graphics card or network adapter to function.
I promise you I’ve been using Linux likely for longer than you’ve been alive, and have used every permutation of Linux, from old school CLI-only shit, to fringe PowerPC YellowDog, to modern Ubuntu/Debian.
Sure thing, friend. I only started on Knoppix and Mandrake. Commodore 64 didn’t have it… I saw in the modern age C64 can run a Unix that takes weeks to boot. 😂 I haven’t managed to put a Debian in dependency hell in about 10 years. 😅
PowerPC YellowDog
Reminds me of swap-trick to install burned Linux for PlayStation 2. I see someone is still compiling kernels for PS2, up to 5.x 😆
i dont know what you are using but the general linux experience hasn’t been like this in years. and even if there is a problem now and then a bit of googling generally is all it needs. the one thing you cannot get around is malware like kernel level anticheats. that’s windows only.
having a backup is good advice no matter what system you use
Yeah, same in my experience: updates do not breaks things in debian-derivatives at least. That’s how I managed “well” without backup. That said, linux support is certainly hit-or-miss, which is usually the bigger problem.
AMD support is baked into the kernel, so you really don’t have to do anything unless you’re on bleeding edge hardware and the drivers are in a version of the kernel your distribution doesn’t ship yet.
Isn’t best practice to install your system on a different partition than /home anyway? Back when I used Linux (and the experience was a bit like they described) I’d just nuke the system partition and reinstall if I fucked something up.
This is why I really don’t want to have to use Linux, but Microsuck just can’t stop with the fucking greed and I’m absofucukinglutly not running anything with recall… :(
Once you get it all setup and proud of your work, make a fucking backup image, because a single update that changes an obscure library in some forgettable package that was part of your install will break everything and you will be pulling your hair out kludging a CLI script to unfuck some other binary that was unimportant, but now has affected another thing that was crucial for a graphics card or network adapter to function.
You’re either running Arch/some other bleeding-edge system without Linux experience (do not recommend) or you haven’t tried Linux in 10 years.
I promise you I’ve been using Linux likely for longer than you’ve been alive, and have used every permutation of Linux, from old school CLI-only shit, to fringe PowerPC YellowDog, to modern Ubuntu/Debian.
Sure thing, friend. I only started on Knoppix and Mandrake. Commodore 64 didn’t have it… I saw in the modern age C64 can run a Unix that takes weeks to boot. 😂 I haven’t managed to put a Debian in dependency hell in about 10 years. 😅
Reminds me of swap-trick to install burned Linux for PlayStation 2. I see someone is still compiling kernels for PS2, up to 5.x 😆
i dont know what you are using but the general linux experience hasn’t been like this in years. and even if there is a problem now and then a bit of googling generally is all it needs. the one thing you cannot get around is malware like kernel level anticheats. that’s windows only.
having a backup is good advice no matter what system you use
Yeah, same in my experience: updates do not breaks things in debian-derivatives at least. That’s how I managed “well” without backup. That said, linux support is certainly hit-or-miss, which is usually the bigger problem.
I don’t know, the last time I tried Linux the fucking Nvidia driver fucked my system a couple times before I said fuck it and went back to 10.
Going to try again with my amd card at some point
AMD support is baked into the kernel, so you really don’t have to do anything unless you’re on bleeding edge hardware and the drivers are in a version of the kernel your distribution doesn’t ship yet.
That’s fantastic news! Nvidia drivers are literally the reason I’ve abandoned Linux easily a half dozen times.
Linus Torvalds, creator of the Linux kernel, can’t control what support Nvidia offers for their own products, but he often shows his opinion of them:
Isn’t best practice to install your system on a different partition than /home anyway? Back when I used Linux (and the experience was a bit like they described) I’d just nuke the system partition and reinstall if I fucked something up.
This is why I really don’t want to have to use Linux, but Microsuck just can’t stop with the fucking greed and I’m absofucukinglutly not running anything with recall… :(