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

  • Laser@feddit.orgEnglish
    15·
    14 days ago

    I’m all for alternatives, regardless of whether I’m gonna use them, but in my opinion, one of systemd’s big advantages is that you’re not relying on scripts for service management; scripts mix configuration with logic and this was a big reason why a lot of distributions switched to systemd in the first place. The init scripts (that they had to write themselves) were sometimes getting very large and complex in order to cover interdependencies (both to other services, but also to eventual mountpoints) and ordering.

    Now, please don’t see this as a general criticism of this init system, firstly I’m not an expert on the subject, second I don’t believe there is the one and true design that covers all cases. My criticism is more towards the reporting about this when comparing to systemd.

    There are comparisons that state that this isn’t the monolith systemd is. From the author’s own blog in comparison to runit:

    nitro favors a monolithic approach, and keeps everything in a single process. This makes it also easier to install for containerization.

    So if you’re really into that “do one thing and do it well” mantra, use something different. Note: personally, I think use what does the job best, and if you think nitro does a particular job better than systemd, go for it. I’d guess that it could be particularly suited better for the last three bullet points in the OP compared to systemd, but that would need to be tested in practice.

    Anyhow, if you hate systemd or another piece of free software, go touch grass.

  • Avid Amoeba@lemmy.caEnglish
    111·
    14 days ago

    I like systemd so much I felt compelled to come here and tell you about it.

  • kaidenshi@lemmy.worldEnglish
    82·
    14 days ago

    The submitter appears to be attempting to stir up controversy by implying the author of nitro “hates systemd”. This is just an alternative init, it has nothing to do with systemd and there is no opinion whatsoever about systemd in the linked GitHub. Subby, quit your shit stirring.

  • Victor@lemmy.worldEnglish
    64·
    14 days ago

    I’m probably very prejudiced but I have a hard time taking someone seriously who has an anime girl as their public avatar. I’m sorry for being an asshole (?), but I admit my faults.

    • Alphane Moon@lemmy.worldEnglish
      53·
      14 days ago

      No, you’re not prejudiced. This is a reasonable take.

      If you release public facing projects (outside of anime and anime adjacent projects), you need a modicum of professionalism.

      Open your own affiliated Mastodon account and pick whatever avatar your want. Release channels should have neutral avatars/graphics/images.