view the rest of the comments
Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
This.
I use single partitions, because since everything is SSD now, partition failures are almost nonexistent. I don't know why; I don't understand the mechanics of why disks are more prone to partition failures, but now when SSD start to fail, it seems as if it is anything except something that can be isolated by position.
But I do isolate by subvolume, and for the reason you give: snapshots. I snapshot root only when something changes, but do hourly snapshots of home. It keeps data use more manageable. Nightly backups, and I never have more than 24 home snapshot at a time.
Write yourself some package manager hook scripts that fire off root snapshots before package upgrades or installation. I keep like 10 of those in addition to my scheduled system snapshots. It makes rolling back a borked update trivial in case I don't have time to fix something that went wrong before important work needs to happen.
snapper does that; I think it's available for most distros, so no scripting necessary. There's an Arch package that takes snapshots before installing any software.
Neat stuff!