this post was submitted on 31 Jul 2023
137 points (97.2% liked)
Linux
48364 readers
1126 users here now
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.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
🎉 Same! I've been looking at Ashos (meta distribution) or just using btrfs snapshots to rollback when I break something.
Yeah rollbacks are probably the best part of immutable OS's, but of almost equal importance is reproducible system configuration, which imo only Nix and Guix do well. Neither snapshots nor Silverblue really manage that yet.
For reproducible configuration in the Arch world, there's a project which always looks good to me: aconfmgr
https://github.com/CyberShadow/aconfmgr
I think Arch+aconfmgr+yadm+btrfs == a pretty solid arrangement.
Though I'm of course itching for first class Bcachefs support...
Yeah. For reproducibility I still use nix. Especially when I have to share my dev environment with a team or to spin up identical servers.
Can you give an example in what kind of scenario you would want "identical servers"? In my head that is where tools like ansible come into play..?
You can achieve similar results with ansible. But I like nix better. It is reproducible. You can think of it like docker.
Nix is also declarative and has rollback. Also, nixos-rebuild is idempotent.
The great thing about Nix is that it achieves reproducibility with the package manager. Container and Ansible depend on taking a system and documenting steps to bring it to the desired state. This state then might deviate over time (e.g. crashing while updating).
But yes, for most practical use it probably doesn't make much of a difference. For me Nix forces me to document what I'm doing, which I might not do for "quick and simple change" on other systems.
My problem with snapshots is that sometimes I break something and notice it way later. This accumulated state at one point breaks something (i.e. I break something). With NixOS I'm forced to do things right, which is also annoying and time consuming.
That's right. I just rely on intuition to create a snapshot just before I think some operation will potentially break the system. (Along with daily snapshots)
It's definitely not as bulletproof and transparent as Nixos. You can see what has changed by doing a diff :)