- cross-posted to:
- linux@programming.dev
- cross-posted to:
- linux@programming.dev
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).
‘Change resistance’ was the standard gaslighting. No one said ‘different bad’, in a time when enterprise linux had just switched from sysVinit to upStart. What they said was “this is built bad and wants to do too much, poorly. We don’t like this.”
And the response was “you’re old, you hate change,” and similar fallacies.
I think you mean “I don’t know how to do this in the normal way, so I’ll try this other thing.”
Plenty of people did. “What’s the point of change?” “I’m happy with Sys-V” “I don’t like Poettering”, “Lennart is too powerfull” and a lot more irrelevant and personal attacks.
Please don’t accuse me of gaslighting whilst gaslighting me in return. I was there, I lived through the worst of the Debian wars and saw some great people leave the project, and a side of some friends that I really didn’t like. But that war is done and I have zero interest in continuing it so I’ll leave this here.