3 ms·
> launchd's documentation is so woefully incomplete it's soul-crushing Interestingly, systemd (which, AFAIK, is influenced in large parts by launchd) goes the
by majewsky 9y ago
> launchd's documentation is so woefully incomplete it's soul-crushing
Interestingly, systemd (which, AFAIK, is influenced in large parts by launchd) goes the exact opposite way and has amazingly complete and well-structured documentation.
- SwellJoe 9y agoI've found that to be true, as well. Say what you will about systemd, but they've really done a good job documenting it. There are also useful blog posts from some of the developers delving into various topics. Nearly every question I've had about systemd (and I've had a lot, as our products interact with the init system tons) has been answered either by the docs or by a blog post by one of the systemd developers. e.g. I recently dug into how to build an inetd style (called "socket activation" in systemd) service. I found pretty good core docs, and a very good blog post with real and useful examples. Learning my way around systemd has just been a good experience, all around. I have my complaints, but doc quality isn't among them. It's a big project, but having it all come from the same folks does lead to a consistency across sub-systems that is rarely seen in the Linux world.