Linux

57888 readers

715 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

106

Hate Systemd? A New Init System(Nitro) Debuts as a Minimalist Process Supervisor for Linux (github.com)

submitted 1 week ago by Pro@programming.dev to c/linux@lemmy.ml

81 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] Badabinski@kbin.earth 11 points 1 week ago (1 children)

I wrote and maintained a lot of sysvinit scripts and I fucking hated them. I wrote Upstart scripts and I fucking hated them. I wrote OpenRC scripts and I fucking hated them. Any init system that relies on one of the worst languages in common use nowadays can fuck right off. Systemd units are well documented, consistent, and reliable.

From my 30 seconds of looking, I actually like nitro a bit more than OpenRC or Upstart. It does seem like it'd struggle with daemons the way sysvinit scripts used to. Like, you have to write a process supervisor to track when your daemonized process dies so that it can then die and tell nitro (which is, ofc, a process supervisor), and it looks like the logging might be trickier in that case too. I fucking hate services that background themselves, but they do exist and systemd does a great job at handling those. It also doesn't do any form of dependency management AFAICT, which is a more serious flaw.

Nitro seems like a good option for some use cases (although I cannot conceive why you'd want to run a service manager in a container when docker and k8s have robust service management built into them), but it's never touching the disk on any of the tens of thousands of boxes I help administrate. systemd is just too good.

[–] TMP_NKcYUEoM7kXg4qYe@lemmy.world 1 points 1 week ago

This does not seem very different from runit, so you probably do things similarly. Dependencies are done by checking if the dependency is running inside the script. Presumably you deal with daemons by execing the daemon, so that the daemon becomes the script, not a separate process.