Like I think all of the Systemd stories, sensational article is sensational. If you actually read what machinectl is, you'll see it has nothing to do with the su command, and it's also not suppose to replace it. Basically, from reading for about 1 minute, machinectl is to execute operations on VMs and containers. Last time I checked, the su command don't do that and have nothing to do with it. Probably someone asked Poettering, "Hey, would be nice to have root shells in a VM"

http://www.freedesktop.org/sof...

Wasn't the point that chroot is as good, and not better, as the normal Unix permission/groups security feature? So, basically, chroot doesn't and isn't designed to add any additional security besides the normal Unix permission/groups security.

https://securityblog.redhat.co...

Firefox and other browsers (and Flash) had 0-day security exploids like forever, but nobody recomends to just stop using the Internet. Also, you can chose to run the Java Applet in a sandbox. There are tons of very useful Japa Apples still there, why should I deactivate Java and stop using them now? How is that 0-day exploid going to affect me in any way? It isn't and it won't, especially because Java Apps ask for permission to be run.

https://sites.google.com/site/...

"The documented format is compatible with the format used in the first versions of the journal, but received various compatible additions since."

So, your last statement is factually wrong, i.e. that you need the version of journalctl that systemd was running. You can use the first version of journalctl and you will be able to read systemd 195 logs. But pracically, it is not the big deal you want it to make.

And what? That was in 2011, and they wrote "At this point we have no intention to standardize the format ..." That quoted document was from the introduction of the journal. It's obviosly that the developers didn't want to freeze the format at that time.

Citation very much needed.
Here is a documentation of the binary log format:
http://www.freedesktop.org/wik...
Systemd offers a C API to access those, an export format for easier parsing, and of course you can access the binary logs directly.
http://www.freedesktop.org/sof...
http://www.freedesktop.org/wik...

I don't get the issue of binary logging. All files on my computer are binary, I always need some sort of program to show me the content of the file on my monitor. And what's the difference if SystemRescueCD ships journalctl alongside grep and emacs to show me system-log files?
The other, systemd's influence over other projects? What? So, if developers of Gnome or KDE decide that systemd brings a feature that they want to use (like systemd-logind) *that's* what you call "system'd influcence over other projects"? What is that igocentric thinking on your part?

I never understand the penchant for people who complain how many tabs other people have open. Is there a rule that you should limit yourself to single digit count of tabs open? But to answer your question, Firefox have since ages vertical tree tabs as plugin, and the lack of such vertical tabs plugin is the reason why I don't use Chrome.

Lying is not a "mortal sin" (sic), where did you get that from? Unbelief is the mortal sin in Christianity and Islam. Btw, I'm not religious in any sense, just pointing that fact out. Or, just to help you to understand the Creationist view point, "Now faith is confidence in what we hope for and assurance about what we do not see." Hebrews 11:1. i.e., faith is evidence in the Creationist view point.

Sure, my email is erwin.mueller@deventm.org
I think it's also on my web site.

Wikipedia is *now* a "trusted data source"? I think humanity is destined for doom.

Wikipedia is not a "trusted data source"? I think humanity is destined for doom.

Also every industrialized country have minium wage, and the majority of them that do, have it about 30% to 50% of GDP per capita. Only the United States is at the bottom, with just 28% of GDP per capita. Germany is on the top with 49%, and we are now currently demaning to increase the minium wage. The minium wage have no impact on jobs, it just makes sure that if you have a job you can sustain yourself. Which will benefit everyone, the small and middle business have more paying customers, we have less crime rate and less of a wellfare state.
http://en.wikipedia.org/wiki/L...

A lot of users left, really? Lets see on Distrowatch.com
2010 9. Arch 768
2011 6. Arch 1134
2012 7. Arch 1201 systemd was introduced
2013 9. Arch 1016
2014 7. Arch 1087
Now 9. Arch 924, with Ubuntu, Debian, Mint and openSUSE on top, probably because of the new releases. All with systemd.
--
2012 22. Gentoo 466
Now 40. Gentoo 313
As far as I can tell, Arch gained popularity for the systemd change, and stood on top through the years, while Gentoo lost a lot of popularity.

Your arguments are all biased and manufactured. That is a frequent observation from me that people who just don't like systemd make up arguments for why it is bad. Quite just like religious people make up argument for why evolution is false. It's also psychology 101 that people form beliefs first and make up arguments later to justify those beliefs. You just don't like systemd. My recommendation is to just give it a try.

"Those you shown are global parameters, not startup scripts."
No, those are the start up scripts.
"SystemD generates diagnostic messages"
Yes, those are extra. There are no diagnostic messages in sysvinit at all. So, you complain that systemd gives you extra tools to debug services.
"systemD instructs you to use some crazy command to parse the binary logs"
All files on a computer a binary and you need some program to read it. The journalctl tool is not crazy, it actually behaves just like grep and tail.
"Usually you can't just disable SystemD, and the tendency (IE it WILL happen), sysvinit will be removed."
The better tools will replace the old and worse tools.
"Precisely. Its not opt-in. And when you manually startup scripts, it captures the useful information the program is outputing *at that instance*."
Let me explain again. If you start a service it will capture sysout and syserr, because otherwise those outputs are lost (like in sysvinit). If you start manually via systemctl those are in the logs and you can see them via systemctl status.
"What we have now, are deamons silently failing and requiring an extra command to understand why"
No, you describe the situation with sysvinit. If a daemon is started on startup the sysout and syserr outputs are lost. Systemd logs them. And also, systemd actually shows you that the daemon failed to start, and blocks other daemons that depend on the failed daemon from starting.