I would also like to "me too" this latest post by another on debian-user list: On 9/10/2014 8:41 PM, Tomasz Kundera wrote:
I'd like to say "me too" as the shortest opinion. Dealing with local networks it is absolutely not important how much time the boot takes. Most machines works all the time. During maintenance reboots I can wait a few seconds more. But the complete lack of simplicity and transparency is horrible. Binary logs are horrible, too. Logs are mostly needed when some troubles arises. In that situation they should be accessible as easy and fast as possible. Often there will be no possibility to start a dedicated binary log analyzer. You need only "more" and "sed" to deal with text logs. systemd with no possibility to stay with SystemV is a horrible mistake.
That embodies a fair bit that is wrong with systemd, certainly by itself, it enough to make many [most?] people prefer to avoid the trials and tribulations that will await them with systemd if at all possible. Of course, I use "less" instead of "more" as it is far more versatile, that is a very good transition to a better option; which cannot be said of systemd. I would also work with vim, awk, grep, zgrep, zcat and other tools, but these only work on non binary logs (excluding the /binary/ status of gzipped files). A.