I believe it’s this: GitHub - snugnug/micros: Microscopic NixOS build designed for embedded environments. [Maintainers=@NotAShelf, @DamitusThyYeetus123]]
1 Like
also RE:
If NixNG, finix and whoever else wants a minimal runtime closure agrees on a common set of overrides and that gets put in a repository, yes, yes it would. It wouldnt be cheap, though we dont have to build all of nixpkgs. Doubt anyone needs a minimal chromium
I’ve been envisioning, for some time, a module system (but not necessarily a package set) that defines common module options that can be used to construct different systemd-less NixOS variants. I was meaning to reply to @aanderse earlier but the general idea (nothing concrete yet, I haven’t had time to sit down and think about a design) would be a module system that can be translated to different init systems’ conventions through processing the options, similar to Nixpkgs’ systemd utilities. Though this is easier to say than it is to implement. In MicrOS we’ve been interpolating shell scripts with services because runit doesn’t exactly have a mechanism like Systemd’s Exec* options. I think this could be standardized somehow across different init systems, but there’re probably edge cases that I’m not aware of.
If there is a common goal to also provide a package set for this, I’m happy to contribute my time and even system resources, i.e., a build server or a cache. I’m also happy to discuss the idea further with anyone interested. MicrOS has stalled due to my own lack of time but I’d really like to work more on this.
3 Likes
As per https://nixos.org/manual/nixos/unstable/#modular-services, in 25.11 NixOS also permits “modular services” under the system.services.* options, which could be consumed by other init systems.
6 Likes