Linux

48372 readers

1665 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

[email protected]

Immutable Operating Systems: Yay or Nay? (self.linux)

submitted 1 year ago by simple to c/[email protected]

50 comments fedilink hide all child comments

I've seen a lot of talks on the benefits of immutable distros (specifically Fedora Silverblue) but it always seemed to me as more of a hassle. Has anyone here been daily driving an immutable distro? Would you say it's worth the effort of getting into?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 1 year ago (2 children)

How long did it take you to migrate from the distribution before and what's your experience in this space in general?

I like the idea of a declarative configuration, but I find it hard to justify when Ansible has the potential to do the job 99% as effectively.

Also, what do you feel are the most "killer features" in nixOS?

[–] [email protected] 5 points 1 year ago* (last edited 1 year ago) (2 children)

I've recently switched over to NixOS in gradual rollouts to my systems:

Stage 0 (~2h):

Installed NixOS with Gnome on my Laptop for testing an getting a feel for it (I prefer testing on bare-metal initially)
Tweaked it a bit via the config: removed gnome apps that came with the preset, installed all programs I needed and tested them

Stage 1 (~3d):

Installed NixOS minimal on my primary system
Set up sway according to the wiki
Bodged together something similar to my previous arch setup, mostly my linking old config files with nix to programs installed with nix

Stage 2 (~4d):

Moved all configs I could from my linked config files to the nix module declarations
Seperated config file into files ordered as like config-tree
Achieved a similar working state to my previous arch install
Moved channel from 22.11 to unstable (rolling release)

Stage 3 (~7d):

Set up home-manager
Finally moved all config declarations into nix modules, no non-nix files left in my config
Also copied the config to my laptop, a single activation and I switched from gnome to sway without any problems

Stage 4 (~21d):

Looked at a bunch of other peoples system configs
Recreated everything as a flake, similar to dunklecat's config from sourcehut
Applied the config to my primay system and laptop
Wrote a bunch more config modules

Stage 4.5:

Wrote some tools to make moving around nix easier for me, but mostly to get accustomed to the ecosystem

Stage 5 (~6d):

Created and applied further system configs for a hetzner server & VMs

Stage 6 (tbd):

Refining my config
Adding further modules

Edit 1 (added personal experience): I'm a computer science student and have been using *nix as a daily driver for half a decade, my previous daily driver was arch for about two years. I spend ~1000h/y coding on non-University or Work related projects. I'm at a point where I can typically pick up a the basics of a new language in two to three weeks and write simple programs with it -> library/specific knowledge comes with usage.

[–] [email protected] 2 points 1 year ago

Nix(OS)'s biggest killer feature for me is that I never had to update, wait for updates or fix updates after setting up the modules properly and getting CI set up for my git repo -> all systems are build before the update is rolled out, if the build fails, the update won't be rolled out. Systems decide for themselves when to update and how they should handle them (i.e. server vs. desktop).

That goes for all my systems: Laptop, PC, Servers and VMs

[–] [email protected] 2 points 1 year ago

Thanks for the insights :) I appreciated

[–] [email protected] 2 points 1 year ago

I like the idea of a declarative configuration, but I find it hard to justify when Ansible has the potential to do the job 99% as effectively.

From my point of view, the strength of NixOS compared to sensible is not that it does the stuff you declared in your configuration. It's knowing that the description is complete and your system does nothing else (because it's basically selectively built at boot). Sure, some options have implications that might not be visible at first glance, but nothing can hide in the long term. You have no such guarantee with Ansible.

Ansible is a good solution, but it doesn't do as much as nix on NixOS.