nix-processmgmt VS not-os

I somewhere saw this project being mentioned: https://github.com/svanderburg/nix-processmgmt

That's nice and it showcases how Nix can create a declarative process management atop a script-based imperative manager. How is your experience with it? Also note that there's https://github.com/svanderburg/nix-processmgmt, a manager agnostic processes management framework supporting s6 among others, but your way seems a bit more straightforward.

There's a project still being developed: https://github.com/svanderburg/nix-processmgmt my understanding is that if home-manager would use it (I don't know if there is even plan to do that, it's not the same author), it would be able to work without needing systemd.

(builtins.fetchTarball "https://github.com/svanderburg/nix-processmgmt/archive/6def8584c6b028c922c550859a07b989d21d6f73.tar.gz")

It's not really clear to me what you are asking. Are you maybe looking for nix-processmgmt? (NixCon 2020 talk: https://cfp.nixcon.org/nixcon2020/talk/TW79FU/)

Hi. I'm new to nix and want to ask if you have an idea how to build an ISO image file of not-os and run it on QEMU virt vanager?

Maybe not-os?

oh oops, I think I was intending to type "crowd source" but I really met "crowd fund".

I do want to finish my FreeBSD cross PR, but is is hard. We already have NetBSD working, including building the kernel, so I think it is better to start there.

I opened https://github.com/cleverca22/not-os/issues/16 because I think that would be the absolute easiest first step, with the fewest moving parts. But I don't know how kernels, even Linux, are packaged into bootable thingies at all.

I also found this: https://github.com/cleverca22/not-os

It's like an OS that has builtin salt/ansible/chef/puppet.

Because Nix language describe the OS instead of what to change/configure it's superior to these tools, and solves the problem that supposedly same machines are drifting apart.

For example if in the CM you tell it to install a package, then change your mind and remove the entry that does it. The package will remain installed.

With NixOS if you remove the package from configuration, it's gone.

I personally really like Nix's building capability. For example I can use it to generate a minimal docker container. It requires some knowledge, but I can also modify compilation options in dependencies (like remove unneeded functionality).

It looks like there's also an option to similarly build lightweight OS images[1]. I haven't tried it yet but looks cool.

[1] https://github.com/cleverca22/not-os

You might want to check out https://github.com/telent/nixwrt and https://github.com/cleverca22/not-os as solutions with similar goals. The former is a promising but yet-unfinished way of using Nix to manage a router, while the latter is a similar way of using Nix to generate an immutable OS image.