- cross-posted to:
- linux@programming.dev
- nix@programming.dev
- hackernews
- cross-posted to:
- linux@programming.dev
- nix@programming.dev
- hackernews
cross-posted from: https://programming.dev/post/47658995
Related discussion:
cross-posted from: https://programming.dev/post/47658995
Related discussion:
Agent…? Uh, okay, let’s just use that word for everything now.
Sorry, where is the part where you built something?
Anyway, NixOS gets a lot of praise. Maybe it’s something I should try if Manjaro doesn’t survive its current drama (though it seems like they have a path forward now).
Yeah, that paragraph is where I stopped reading lol
Blog post aside, NixOS is fantastic. Once you get the Nix DSL down, it makes everything so smooth once you know how to configure your system. The learning curve for me came not from the packages, but learning how to set up system/program configurations using
configuration.nix, instead of the standard config files. But once you get that down, you can rebuild essentially the exact same system from a single file. I use it for my worker nodes on my server cluster, and it makes setup of new nodes a dream. Definitely recommend.I’ve been using NixOS for a year now, and I did use LLMs to set up a large part of my configuration: It’s absolute amazing being able to share 1 configuration between multiple machines.
I also added a
Justfileto hold a bunch of common commands, so I can never forget them :DJust start out by throwing your
hardware-configuration.nixandconfiguration.nix(from/etc/nix/configuration, IIRC) into a repo, andsudo nixos-rebuild switchas starting command (in that repo).Also yes, each host will need its own hardware-configuration, but they can share a configuration.nix (to some extent), but just start by adding a list of programs from https://search.nixos.org/packages, oh and @vimjoyer IS the documentation.
When installing a package is too hard, one simply should not use a PC. Maybe the nursing home would be a better place.