dinit VS systemd

The author has a high-level overview doc here: https://github.com/davmac314/dinit/blob/master/doc/COMPARISO...

Now, of course, with service management the devil is in the details, so before you use something as system-wide init, I find it useful to ask yourself: How do they restart services? Do they give up at some point? How do they notify administrators of failures? Do they detect crashloops? How configurable is the logger? What CLIs are there to debug the state of the system (which service was first to fail, where is its definition)? How to make ephemeral or parametrised services? How to add pre-start, post-start, pre-stop, post-stop hooks? Can you use environment variables in your commands, and where do they come from?

I don't think you can find answers to some of these questions in docs. Once you do learn the answers, they may be disappointing - I indeed found myself quite disappointed in systemd after having to debug many failed-to-boot machines. With s6, I never run it, but there are few choices that raise eyebrows, e.g. the restart delay is hardcoded in source code to be 1 second. With dinit, I have yet to finish reading all its manpages, but at least timeout and restart policies are configurable.

Not to be confused with https://github.com/davmac314/dinit

Still, I applaud efforts like s6 and Dinit as competition is a good thing in general. I hope they'll continue to be improved upon until they've become viable alternatives to systemd for most users.

You can download dinit from github https://github.com/davmac314/dinit. (also read everything about it) Do a simple make && make install which should install it to /sbin/dinit No need to remove systemd or openrc. /sbin/init should be symlinked to whatever init system you use. Read the instructions on dinits page. All the services go into /etc/dinit.d. And you can "dinitctl enable servicename" to enable it. I threw the services I have on my system up at https://gitlab.com/fictitiousexistence-public/dinit-gentoo/ You can copy them and enable / disable whatever you need. Most services I jacked from artix since they have a supported instance of dinit.

It got mass-adopted while being imperfect, so that's to be expected. Thankfully its inception and the criticism that followed have paved the way for the likes of dinit and s6.

this page by Davin McCall, creator of dinit.

I use dinit do manage services on my home server. One of them is Caddy, that shares TLS/SSL cert state with my remote server by using Redis on said remote server. However, since this means that I need to have established a remote connection first before starting Caddy, I would like to know of a method to check if tailscale has in fact finished connecting.

I've used a ton of improvements but I know this community knows a lot more about some parts than me. So here I come. I'm currently using efibootmgr to create an efistub to bypass grub. Using base-minimal with ncurses so terminal apps work. Also I use this in my /etc/dracut.conf.d/local.conf: hostonly="yes" omit_dracutmodules=" network plymouth " And that works perfectly. Don't know exactly what network or plymouth are for but they are not strictly required. Also I use dinit: void_dinit, dinit. This works perfectly fine and works like expected after a little troubleshooting. Also for making dinit about 2x faster is swapping coreutils to sbase. I only use ls from gnu coreutils which is something I may want to switch but I haven't come to finding a good alternative to ls that has colors (exa exists but is 11x as big) Things that I could think of that could improve stuff are: kernel, maybe initramfs. Maybe something else I've looked over. What is all made by GNU anyway? I may have forgot something Void Linux uses.

systemd: Yes; it's awaiting its "PipeWire". Thankfully, the likes of s6 and dinit are very promising. Though I can actually appreciate that systemd is addressed. As ultimately it helps in raising awareness that will benefit whatever software will replace it eventually.

Arguably this is less troublesome to solve compared to the other concerns. As we're inevitably waiting for the system supervision suite that will be to systemd what PipeWire has been to PulseAudio. I'm very optimistic about this as both s6 and Dinit are shaping up lovely.

No, the OP was not sent any harassment, the OP _did_ the harassment as it can be seen in the tweets. I mean, they are right there, just click on the links you shared. One of the OP's followers even openly called for the assassination of the project maintainer, and you have the galls to defend him? This is truly deranged stuff.

And again, there is no "vulnerability", there is simply a person that doesn't know how Linux works and has learned something new. Which again it's fine, nobody knows everything and we all learn new things everyday, it's just that normal and sensible people don't use that to make grand claims on social media and start harassment campaigns culminating in death threats.

Professional security researchers responsibly report real issues using the appropriate channels, such as defined at: https://github.com/systemd/systemd/security/policy this is not the work of a researcher, this is a grifter looking for self-promotion on social media.

> 3. even `adduser` will not allow it by default

5. useradd does allow it (as noted in a comment). 6. Local users are not the only source, there things like LDAP and AD.

7. POSIX allows it:

* https://github.com/systemd/systemd/issues/6237#issuecomment-...

> I for one love to type out 13 extra characters

FWIW, systemd is normally pretty good at providing autocomplete suggestions, so even if you don't want to set up an alias you'll probably just have to type `--b ` to set it.

> I wonder what random ASCII escape sequences we can send.

According to the man page source[0]:

> The color specified should be an ANSI X3.64 SGR background color, i.e. strings such as `40`, `41`, …, `47`, `48;2;…`, `48;5;…`

and a link to the relevant Wikipedia page[1]. Given systemd's generally decent track record wrt defects and security issues, and the simplicity of valid colour values, I expect there's a fairly robust parameter verifier in there.

In fact, given the focus on starting the elevated command in a highly controlled environment, I'd expect the colour codes to be output to the originating terminal, not forwarded to the secure pty. That way, the only thing malformed escapes can affect is your own process, which you already have full control over anyway.

(Happy to be shown if that's a mistaken expectation though.)

[0] https://github.com/systemd/systemd/blob/main/man/run0.xml

[1] https://en.wikipedia.org/wiki/ANSI_escape_code#SGR_(Select_G...

bash & zsh are supported by upstream: https://github.com/systemd/systemd/tree/main/shell-completio...

the right person to replace sudo, not: https://github.com/systemd/systemd/issues/6237

PS: https://pwnies.com/systemd-bugs/

https://github.com/systemd/systemd/issues/32028#issuecomment...

There are some very compelling arguments made there if you care to read them

Maybe it was because you weren't pointing out anything new?

There was a pull request to stop linking libzma to systemd before the attack even took place

https://github.com/systemd/systemd/pull/31550

This was likely one of many things that pushed the attackers to work faster, and forced them into making mistakes.

The PR for changing compression libraries to use dlopen() was opened several weeks before the xz-utils backdoor was revealed.

https://github.com/systemd/systemd/pull/31550