A big part of learning Linux is screwing up computers and starting over.
-
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
-
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.
100%
The alternative being variations on:
years experience.Please run
sfc /scannow.You can find more help at [Irrelevant KB URL].
Please rank me 5 stars.
Ticket closed
-
That also sounds like a good way to stop learning!
Not quite. But sorta, yeah.
Learning to "not fuck with it" or ways to do so and rollback are valid lessons themselves.
Being able to segregate "production" and "development" environments is very valuable.
-
My crippled kernel count is around 6, how about yours?
Once you break it a few times, you start to understand the value of btrfs or ZFS snapshots.
-
My crippled kernel count is around 6, how about yours?
Just did a fresh install after attempting to migrate from a proxmox VM to baremetal (turns out my mobo only supports UEFI and after spending an hr trying to convert I just gave up and reinstalled)
-
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.
never had to start over -
My crippled kernel count is around 6, how about yours?
Making errors and analysing them to figure out what went wrong and why is a huge part of learning. You can only learn so much from theory, some things can be learned best by trial and error and the experience gained from it.
When I started with Linux I did choose to use Gentoo Linux because it was the most complex and complicated option, so I had the most opportunities to learn something by ducking up!
-
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 is a good piece of software doing a tired trick.
The new hotness is copy on write file systems and snapshots. I can snapshot, instantly, then do a system update and revert to the previous snapshot also instantly.
Instead of using symlinks files, like Timeshift, the filesystem is keeping track of things at the block level.
If you update a block it writes a new copy of the block (copy on write). The old copy is still there and will be overwritten unless it is part of a snapshot. Since the block is already written, snapshots don't require any data to be copied so they're instant.
Once you finish the system update, all of the overwritten blocks are still there (part of the snapshot) and reverting is also just a filesystem operation, theres no mass data to be copied and so it is also instant.
It does use disk space, as allocated blocks AND snapshotted blocks are stored. It uses less than Timeshift though, since Timeshift copies the entire file when it changes
ZFS and btrfs are the ones to use.
-
-
Not quite. But sorta, yeah.
Learning to "not fuck with it" or ways to do so and rollback are valid lessons themselves.
Being able to segregate "production" and "development" environments is very valuable.
Being able to segregate "production" and "development" environments is very valuable.
This is a best practice that pretty much everyone, eventually, discovers on their own.
-
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
Ah Chroot bro
-
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.
Been looking for a DR system for Ubuntu or mint, need to look into it myself but would like some feedback if this could be the right ticket.
I just bought a raspberry pi 4 to host plex, I'm sure I could get it to do backup and restore too. Looking into it
-
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!
"Starting over" is how we learnt Windows in the 90's too
-
"Starting over" is how we learnt Windows in the 90's too
I'd just re-install Windows over the top of the fucked up install normally. It was a bit easier to recover from, and a bit harder to fuck up
-
My crippled kernel count is around 6, how about yours?
I remember managing to installing two DE one above the other, and having them, somehow working at the exact same time. That was trippy.
I didn't even know how I did it.
-
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.
OpenSUSE Tumbleweed Gang.
The only distro I haven't been able to break after 6 months (well, I have, but I've been able to snapper rollback every time) -
Timeshift is a good piece of software doing a tired trick.
The new hotness is copy on write file systems and snapshots. I can snapshot, instantly, then do a system update and revert to the previous snapshot also instantly.
Instead of using symlinks files, like Timeshift, the filesystem is keeping track of things at the block level.
If you update a block it writes a new copy of the block (copy on write). The old copy is still there and will be overwritten unless it is part of a snapshot. Since the block is already written, snapshots don't require any data to be copied so they're instant.
Once you finish the system update, all of the overwritten blocks are still there (part of the snapshot) and reverting is also just a filesystem operation, theres no mass data to be copied and so it is also instant.
It does use disk space, as allocated blocks AND snapshotted blocks are stored. It uses less than Timeshift though, since Timeshift copies the entire file when it changes
ZFS and btrfs are the ones to use.
Didn’t quite follow what you were saying completely.
Are you suggesting a new program over time shift or change the file system type like ZFS and Btrfs?
I’m using Ubuntu and not sure if I seen those before. -
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.
I wanted to give OpenSuse Tumbleweed a go yesterday, but the live USB got stuck at “Loading basic drivers” so I couldn’t even get to being able to install it.
-
That also sounds like a good way to stop learning!
wrote on last edited by [email protected].
-
My crippled kernel count is around 6, how about yours?
I haven't majorly fucked up any recent systems (almost botched the steam deck once or twice but nothing that required a reinstall), but god 10 years ago I probably reset my arch dual boot like five times lmao
