nina

> To be clear, I don't want to use meson as the default build system for dinit. I prefer that dinit can be built on a minimal POSIX system without...

as far as I can tell this is going to need a lot more to work correctly

i was thinking the network.target could just come up regardless of the status of firewall in this case, but i'm fine with any behavior here (the user is not meant...

it means the correct fix is to preserve the existing semantics of integer wraparound, your logic here is sketchy and does not look like it behaves identically you can preserve...

i guess that could work, but yeah it's a tad clunky (maybe it wouldn't matter that much in my use case though)

i think this could even be done with just two services? the readiness service would be scripted and depend on the actual process service; if the process service does not...

this can actually be implemented with one command, i've already done so for what i had in mind: https://github.com/chimera-linux/dbus-wait-for so i think there is no need to have this feature...

I was able to get the machine to hang (randomly after about 2 days of uptime, didn't need to do anything like play video or use qemu) because of apparently...

yes: https://bugzilla.kernel.org/show_bug.cgi?id=204145

i will re-review this when i get a bit more time