this post was submitted on 26 Aug 2025
102 points (85.9% liked)

Linux

57752 readers
409 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

Related Communities

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

founded 6 years ago
MODERATORS
 

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
[–] dgriffith@aussie.zone 40 points 3 days ago (1 children)

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 13 points 3 days ago (1 children)

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 12 points 3 days ago (2 children)

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 21 points 3 days 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.

[–] Arcane2077@sh.itjust.works 3 points 3 days ago

Oh. That’s fucked up. Appreciate the info