From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
"Except when something breaks after an odd update once or twice per year"
You don't need snapshots, except for the moments when you do. The point of snapshots is that they're so cheap that you can let them roll on their own and only care about them the day your system breaks.
A broken system is no big deal for me, I can easily get up and running after a failed update. My data is also mirrored to my Nextcloud instance.
You’re not alone. I do use snapshots for failure protection but I also use it when I know I’m likely to induce a failure by running an experiment.
It’s also just as valid to not use the snapshot feature at all. Perhaps you value data integrity, for example, through the use of full checksums enabled by the design.
Your system and the software it runs belongs to you and is in your service.
I've done that before when debugging system issues. Create a snapshot before and after the issue, and diff the files to see what changed.
I also took a snapshot before updating to a new version of Mint, realised it broke a bunch of stuff and rolled back.
Honestly, I wish btrfs was the default in many places since taking a snapshot is so cheap and easy.
That sounds fine, but isn't this also what LXC is for?
It could be a sensible approach, but with a snapshot I am free to tinker with every aspect of the system knowing that I can revert everything with a reboot.
Which is exactly how the normal flow of snapshots work too. Except no initial reboot to start tinkering
I'm not using btrfs on my main workstation, but I make a fresh backup whenever my distro prompts me to update. I haven't needed a backup in years though, because I'm experienced in doing even experimental things the way they should be done (like not using sudo in reflex for any permission error or using /usr/local/ or .local/ instead of mixing custom stuff with OS stuff etc)
This is precisely what Opensuse MicroOS, Aeon, etc do, with the one difference that they use the snapshots as a fallback rather than a test env.
You restart and reboot into the snapshot? Maybe KVM and ssh into it could be a nicer workflow?
Yes, I reboot into the snapshot. I need to tinker into a copy of my system and I think there is no easy way to boot into the snapshot with a virtual machine.
Why not do both?
I use a script in cron that uses timestamps as snapshot names, and deletes old ones. Then I also take a snapshot with a timestamp right before doing anything dumb.
You could even make a script called mksnap that figures out what zfs/btfs you're in on the current folder and auto-snaps it.
This is an option, but I really do not need periodic snapshots.
+1, I do the same.
Glad to read that.
I wrote snapshot hooks for Arch that fire before installing or upgrading packages and I have a simple shell alias that I can use to fire off a manual snapshot any time I need one. If a package breaks in an inconvenient way and can't just be dowgraded back to function or I have some other time pressure I can just point my root partition at a clone of my most recent snapshot and reboot to roll back. I don't usually bother rebooting into a cloned snapshot to test changes as I can just perform the same steps to roll back and the automated rolling snapshots mean I don't need to baby anything to have the same protection.
This is also a sensible approach.
I do not use snapshots despite using BTRFS due to low disk space
i prefer nix-shell -p or distrobox