[QUrprUd1nCeicw]

I have bad news for you, every alternative is going to be the same or worse. There's no good and clean solution for early boot services. The Linux kernel expects you to handle any of those issues in userspace with a userspace daemon like dbus. If you're upset the documentation is sparse, well, welcome to open source.

Nobody is "screaming" at you to stop using libdbus. The issues with it are actually spelled out in the docs. Here's what they say:

>The low-level API documented in this manual deliberately lacks most convenience functions - those are left up to higher-level libraries based on frameworks such as GLib, Qt, Python, Mono, Java, etc. These higher-level libraries (often called "D-Bus bindings") have features such as object systems and main loops that allow a much more convenient API.

>The low-level API also contains plenty of clutter to support integration with arbitrary object systems, languages, main loops, and so forth. These features add a lot of noise to the API that you probably don't care about unless you're coding a binding.

So unless you really have your own object system, language and event loop, you shouldn't bother with using libdbus. Use literally any of the other bindings of which there are many. The glib one is only going to be good if you're already using glib's event loop and object system.