cross-posted from: https://programming.dev/post/36342010
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).
Whatever works for other people I guess. A good Linux administrator is a person who can work with the default configuration on their OS, and I am trying to be that person and eventually learning inside-outs of systemd.
Why do you have to have this xor that? Why can’t I like both? I’m sure both have use cases where they work best.
Drop the hate already.
I love
systemd!Hate Microsoft et al., dislike software.
Nice.
I got used typing “sudo service --status-all”
then got used to typing “sudo systemctl list-unit-files --type=service”
now a new one to learn “sudo nitroctl list”
looks simpler
That can only be a good thing for my gnarly arthritis fingers.
What’s the point of all of these init systems if all we ever get are systemd services? You have to manually supervise all services if you’rw not using systemd which is really annoying.
We have so many wheels in linux, just choose the one you like because some Linux user love to reinventing the wheel over and over and over again
This is what systemd is doing. Inventing a set of wheels suitable for most distros
OpenRC works just fine for me
