- cross-posted to:
- linux@lemmy.world
- cross-posted to:
- linux@lemmy.world
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).
No, but the weirdos who insist on spelling it “SystemD” always seem to hate systemd.
systemd is pretty great. I tend to start long-running processes as user services, and I’ve even taken to starting some apps that give an old laptop trouble with
systemd-run
and a slice with some memory restrictions. Easy peasy, works great, all declarative, no wibbly-wobbly shell scripts involved.More like system deeznuts!
(Sorry, I just wanted to say that. 😅)
“SystemD”
@Pro @syklemil I don’t get it either. I tried asking around in the past and it seems to come from a hate for Lennart, which gets hated for creating systemd… Something like that. It didn’t really make sense. I’m interested in newer alternatives of course but I personally use systemd all the time since 2016 at least and I don’t see any problems with it