Nitro is a tiny process supervisor that also can be used as pid 1 on Linux.
There are four main applications it is designed for:
- As init for a Linux machine for embedded, desktop or server purposes
- As init for a Linux initramfs
- As init for a Linux container (Docker/Podman/LXC/Kubernetes)
- As unprivileged supervision daemon on POSIX systems
Nitro is configured by a directory of scripts, defaulting to /etc/nitro (or the first command line argument).
It’s seems like a nice side project for somebody to get to know how init systems work, but advertising it as a systemd replacement? That’s a bit… ambitious? I wish the author a lot of fun writing this, but advertising it with “hate systemd?” is putting the carriage in front of the horse.
Nowhere in the linked GitHub does the author say anything about hating systemd. That is purely the submitter’s bias.
I see how the sentence structure can lead to confusion. It was indeed my intention to say that the submitter is advertising it with “hate systemd” not the author.
Looks promising. This bullet point in particular caught my eye:
- Efficient event-driven, polling free operation.
I wonder if this implies a service dependency graph, which IMHO is the most valuable thing about systemd’s design. I would welcome a small, noninvasive init system with that feature.
Hate Systemd?
No, why would I?
Systemd doing everything at once breaks the “do ONE thing and do it well” philosophy of linux.
People keep on repeating that but “and do it well” was never part of the deal. Also, it used to be “and read my mail.”
