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

  • DigitalDilemma@lemmy.mlEnglish
    93·
    1 day ago

    Two groups of people went to war over a difference of opinion.

    1. New! Bad! Different! Change!

    2. Hey, this works better than the old way. Let’s use this instead.

    • Ferk@lemmy.ml
      3·
      9 hours ago

      You could equally mischaracterize it the other way around:

      1. Hey, this works worse for my workflow than before. I don’t want to use it.
      2. New! Different! Change! Good! Put everywhere!
      • DigitalDilemma@lemmy.mlEnglish
        3·
        6 hours ago

        Fair, and representative of some opinions certainly.

        But change, change is constant. Resist it and end up poorer and more bitter.

        • Ferk@lemmy.ml
          1·
          5 hours ago

          That can be true… but it depends on the change… emptying your bank account is a change that would make you poorer, and having all those who love you die would be a change that is likely to make you bitter (or at least, sad).

          Also, a lot of ancient software introduces change with relatively frequency… the Linux kernel itself is in constant change, introducing new features, despite it having very strict rules concerning backwards compatibility.

          The reason there was disagreement wasn’t about whether the new thing is good/bad just because it’s “New! Different!”… but about whether it was actually a good change or not.

          In the same way, just because nitro is the new init system in town (a change from the current status Quo) does not mean it necessarily is better/worse, right?

          Also, I remember that before systemd there was a lot of innovation when it comes to init systems… most distros had their own spin. And more diversity in components that now are part of systemd. I’d argue that ever since systemd became the de-facto standard, innovation in those areas has become niche. One could argue that there’s less change now, distros are becoming more homogeneous and more change-adverse in that sense.

    • muusemuuse@sh.itjust.worksEnglish
      3·
      20 hours ago

      Dude if you want to start a holy war with the Linux community over your first point, just mention Rust.

      -dodges rotten fruit-