sudo VS turnstile

Side note that I've always found interesting: sudo is almost entirely maintained by one dude: https://github.com/sudo-project/sudo/graphs/contributors

The n=2 case also occurs in the commit: https://github.com/sudo-project/sudo/commit/7873f8334c8d3103...

And indeed, the two values ate bitwise complements.

One feature they didn't mention they left out was the ability to run `make me a sandwich` (https://github.com/sudo-project/sudo/blob/main/Makefile.in#L...)

It's (kind of) back - https://github.com/sudo-project/sudo/commit/9757d29a24ac1872872cf09757b0439c54089707

└───────────────────────────────────────────────────────────────────────────────────────┘

As a comparison, this is the output for https://github.com/sudo-project/sudo:

       0.0439 secs

Complete list (can be found here, files ins_*.h):

Fun fact, the “incident will be reported” message was close to being removed from sudo recently: https://github.com/sudo-project/sudo/commit/6aa320c96a37613663e8de4c275bd6c490466b01

Consolekit is good, but there's a new portable replacement being created called turnstile with even more features, i suggest you check it out: https://github.com/chimera-linux/turnstile

artix support for all the inits is half-baked because they essentially do the bare minimum required to get things booting in a way equivalent to what a classic sysv-style boot would be, and then write service files against that core set, but without ever considering anything beyond that - you can easily tell the difference with dinit which i've seen many artix people talk about - artix dinit implementation is based around the sample service files that come with dinit and not only do not properly utilize dinit to its full extent, but also do not bother to provide any sort of reasonable infrastructure for other services to use, or put any effort towards having a standard service set that multiple distributions could use so that upstreams can easily provide compatible dinit service files - meanwhile chimera has its https://github.com/chimera-linux/dinit-chimera suite, which implements a flexible set of oneshots, support for service targets that can be used for reliable ordering, support for systemd-compatible binfmt files and other helpers and so on, all while ensuring it can be used in a cross-distro manner, as well as https://github.com/chimera-linux/turnstile which provides first-class user service support and session tracking so that you can have reliably managed user processes (e.g. dbus session bus, sound server, etc) and so on

eventually https://github.com/chimera-linux/turnstile should reach practical feature parity with logind (minus seat management, which can be done with libseat/seatd), after which elogind may be removed (but that will require existing things to be ported over)