4 ms·

Your "much written better than I can" article is about Upstart, not Systemd. They're unrelated init daemons, and it seems like many of the complaints in the art

Your "much written better than I can" article is about Upstart, not Systemd. They're unrelated init daemons, and it seems like many of the complaints in the article relate specifically to upstart (event-triggered services with no dependencies, minimal scripting support, killing daemons, not all daemons managable by upstart) but do NOT apply to systemd. Systemd has service dependencies, support for old-style init scripts, and can stop daemons with arbitrary commands. Are you confusing the two init systems? On the other hand, this would be nice: "There is no tool that will print out a dependency map." It's also pretty trivial to implement with a little shell script and graphviz.

dredmorbius 14y ago
Point. I'd linked that off another discussion I'd had some months ago and failed to re-read it with full_comprehension bit set.
fmoralesc 14y ago
> There is no tool that will print out a dependency map. systemctl dot | dot -Tsvg > systemd.svg
- oofabz 14y ago
  Nice, here's the result on Mageia 2: http://frammish.org/systemd.svg http://frammish.org/systemd.svg
  - rwmj 14y ago
    I did a PNG of the Fedora boot process and it's 28 MB and 27852x4091 pixels :-(
dredmorbius 14y ago
And the article I had in mind to post: Juliusz Chroboczek: A few observations about systemd http://lwn.net/Articles/453004/ http://lwn.net/Articles/453004/ Editorial / discussion at LWN: http://lwn.net/Articles/452865/ http://lwn.net/Articles/452865/ And for the record: I'm not particularly much a fan of upstart, but it annoys me somewhat less than systemd.