- cross-posted to:
- Technology@programming.dev
- cross-posted to:
- Technology@programming.dev
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 must log in or register to comment.
God help me if I ever feel this passionate about systemd.
I love
systemd!I’m getting to old for this shit
Why do you have to have this xor that? Why can’t I like both? I’m sure both have use cases where they work best.
Drop the hate already.
Whatever works for other people I guess. A good Linux administrator is a person who can work with the default configuration on their OS, and I am trying to be that person and eventually learning inside-outs of systemd.
OpenRC: Am I a joke to you?
I got used typing “sudo service --status-all”
then got used to typing “sudo systemctl list-unit-files --type=service”
now a new one to learn “sudo nitroctl list”
looks simpler
That can only be a good thing for my gnarly arthritis fingers.
I mean, aliases do exist. For example, with my typical alias schema I might shorten it to
sudo syc lsu-s. But yeah, on foreign systems (e.g. random VPS’s) I can see your point.Thank you cravl
Much appreciated
PoetteringD commands are too damn long
Also automatic paging can go fuck itself
Systemd killed my parents.
Systemd made me bald, and killed my cat.
OpenRC works just fine for me
We have so many wheels in linux, just choose the one you like because some Linux user love to reinventing the wheel over and over and over again
This is what systemd is doing. Inventing a set of wheels suitable for most distros
*Reinventing
What’s the point of all of these init systems if all we ever get are systemd services? You have to manually supervise all services if you’rw not using systemd which is really annoying.
I’m a very mid-level Linux user. I use systemd because I’m just not familiar with how init systems actually work. I love that the choice is there, but I think systemd has it’s place with users like me that get confused.
That being said, I did run Dracut on EndeavourOS because it was recommended for that distro. I never dived into it to see what the exact difference was, though I do remember running into some things I needed to do that Dracut did differently. There may come a day when I dive into inits, but for now I’m just happy if my system boots to desktop.
Dracut is an initramfs generator, not an init system. They do completely different things. You were still using systemd as an init system.
And I rest my case, lol. I don’t even know the difference between init and initramfs. It’s definitely a hole in my knowledge and I should know it going down the line, but I need the right time.
I’m here and there on what I want to learn at any moment. It’s not like I can’t learn, but it’s all about what interests me at the time. I learn things in a scattered manner, which admittedly is a horrible way to learn but its just how my brain works.
Inits are simple. If you know gnu make, it’s about as complicated as you can make an init.
SystemD is not just an init. That’s the problem.
Hate Microsoft et al., dislike software.
Nice.
insert xkcd picture about standard
