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

  • Dave.@aussie.zone
    link
    fedilink
    arrow-up
    36
    arrow-down
    2
    ·
    19 hours ago

    Does anyone actually hate systemd?

    It’s a little too monolithic and kitchen-sink-including for my liking. It doesn’t feel like the “do one thing and do it well” style, it has a pretty large attack surface as a result.

    Oh, and binary log files.

    • Arcane2077@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      11
      ·
      19 hours ago

      It’s a little too monolithic and kitchen-sink-including for my liking. It doesn’t feel like the “do one thing and do it well” style, it has a pretty large attack surface as a result.

      That makes sense. I could see how that would irk a lot of people, but I’d personally trust the widely used, intensely scrutinized, load-bearing, open-source processes, over a lesser known one.

      Oh, and binary log files.

      Yeah those are great… Or do we dislike those too? 🙃

      • nyan@sh.itjust.works
        link
        fedilink
        arrow-up
        11
        arrow-down
        1
        ·
        16 hours ago

        There are a lot of command-line tools for text, like grep and sed, that don’t work on binary files. Whether this matters to you depends on your workflow. (I use grep a lot.)

        • Badabinski@kbin.earth
          link
          fedilink
          arrow-up
          14
          ·
          16 hours ago

          Just journalctl | grep and you’re good to go. The binary log files contain a lot of metadata per message that makes it easy to do more advanced filtering without breaking existing log file parsers.