GitHub - leahneukirchen/nitro: tiny but flexible init system and process supervisor
github.com
tiny but flexible init system and process supervisor - leahneukirchen/nitro

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).

  • Pro@programming.devOPEnglish
    511·
    1 day ago

    Every Linux user actually hates SystemD, but we pretend to like it to show superiority over other Operating Systems.

    • jim3692@discuss.online
      4·
      1 day ago

      Having given a shot to OpenRC on Alpine systems, I would say that I prefer systemd for creating and managing services.

      I like its unified logging, which extends even beyond the host, integrating the logs of nspawn containers. I like its tmpfiles, which allows configuring temporary files, without writing scripts that create/cleanup them.

      I have to admit, however, that I don’t like all of its subsystems. For example, I don’t want networkd and resolved anywhere near my configuration.

      • Auli@lemmy.caEnglish
        2·
        1 day ago

        I love networkd only issue is lack of documentation. Still can’t believe so many systems are using an unmaintained DHCP client. One of the reasons I even bothered is I didn’t like using the unmaintained one.

    • Auli@lemmy.caEnglish
      1·
      1 day ago

      I like it. Good logging easier to write and trouble shoot start up scripts.