A big part of learning Linux is screwing up computers and starting over.
-
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 ¯\_(ツ)_/¯
This is the way!
-
My crippled kernel count is around 6, how about yours?
Another big part is learning how to set it up in a way that it's functional and productive the first time and then STOP FUCKING WITH IT.
-
My crippled kernel count is around 6, how about yours?
i broke debian on my plex server and said fuck it and migrated to endeavor because im more familiar with arch
-
My crippled kernel count is around 6, how about yours?
It do be like that, at least for the first couple years, and typically with decreasing frequency.
-
The "starting over" part is what made it take so long for linux to "stick" with me.
Once it became "restore from an earlier image", it was a game changer!
Tell me more
-
Tell me more
Timeshift was a gamechanger
-
They died for a reason, for yor growth
True, sacrifices on the altar of the God Sysadmin, and their divine mount Er'orreport
-
Timeshift was a gamechanger
Timeshift itself borked my shit up. I had to reinstall all registered packages to fix its fuckups..
sudo aptitude reinstall '~i' -
Timeshift itself borked my shit up. I had to reinstall all registered packages to fix its fuckups..
sudo aptitude reinstall '~i'While only once, timeshift destroyed my bootloader. Don't update and reboot before a meeting, kids
-
My crippled kernel count is around 6, how about yours?
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.
-
While only once, timeshift destroyed my bootloader. Don't update and reboot before a meeting, kids
My test of Timeshift was pretty simple and straightforward.
-
Fresh install Linux Mint
-
Install most of the main software I wanted.
-
Do a Timeshift backup.
-
Install some extra software I didn't necessarily need, but might want to use someday.
-
Restore the backup from step 3.
Results: Everything from step 4 was still registered as installed, but almost nothing from step 4 actually worked.
So I brute force reinstalled everything in place, and haven't used Timeshift since. I'm perfectly comfortable using the terminal, and at worst a live boot media, to fix any issues that might come up.
-
-
Timeshift itself borked my shit up. I had to reinstall all registered packages to fix its fuckups..
sudo aptitude reinstall '~i'I also can't get over the fact that it doesn't understand RAID or filesystems somehow.
-
The "starting over" part is what made it take so long for linux to "stick" with me.
Once it became "restore from an earlier image", it was a game changer!
The starting over part actually contributed to me continuing to use linux tbh. Trying out a new distro, figuring out how to use it, and building a new user interface each time I killed my system kept me engaged with linux beyond its utility. It functioned essentially as a way to learn about computers and as a creative outlet. I don't fuck around and find out as much as I used to but I still swap distro every year or so.
-
Another big part is learning how to set it up in a way that it's functional and productive the first time and then STOP FUCKING WITH IT.
That also sounds like a good way to stop learning!
-
My crippled kernel count is around 6, how about yours?
Bricking hardware is a form of enrichment for me.
-
The starting over part actually contributed to me continuing to use linux tbh. Trying out a new distro, figuring out how to use it, and building a new user interface each time I killed my system kept me engaged with linux beyond its utility. It functioned essentially as a way to learn about computers and as a creative outlet. I don't fuck around and find out as much as I used to but I still swap distro every year or so.
It was similar for me, but not quite the same. The thing I hated was starting from scratch. I'm very much not a distro hopper. Back in the day, I enjoyed the challenge of trying to troubleshoot issues and get the system working again, and that kept me interested, but eventually, I'd hit a problem I couldn't resolve, and I'd have to start again from scratch, and at that point, I'd just go back to Windows.
Now, I still get to do the same thing. If I break it, I get to learn how I broke it and try and fix it, and I find that process compelling. But because I'm using btrfs restore points now, I don't get to the point where I have to start again from scratch. So I can work at solving it to the limit of my abilities, with confidence that if I can't work it out, it's not a huge issue.
-
The "starting over" part is what made it take so long for linux to "stick" with me.
Once it became "restore from an earlier image", it was a game changer!
My game changer was circa 2014 when I broke something and got dropped to a basic shell and for the first time instead of panicking and immediately reinstalling I thought for a moment about what I had just done to break it, and undid the change manually. Wouldn't you know it booted right up like normal.
The lesson here: if it broke, you probably broke it, and if you know how you broke it, you know how to fix it.
-
My crippled kernel count is around 6, how about yours?
-
My crippled kernel count is around 6, how about yours?
OpenSuse Tumbleweed helps because you can create a btrfs snapshot at any moment and then roll back to it if you get in trouble. And it does this automatically whenever you update the packages.
-
My crippled kernel count is around 6, how about yours?
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
