The SystemD crowd are windows devs who hate 8 so much, they finally decided to get into linux. Sadly, they want linux to work like windows, so they foist their shit into it. It does make boot times faster: something sysadmins usually don't give a shit about since you don't reboot servers. Red Hat wants systemD because it will let them abstract linux (the kernel) away to the point where they can control it instead of "the community". In addition, several genuinely nice tools, UUID for disks, are being folded into SystemD so, in order to get those tools, you *must* also use SystemD.
Isn't that supposed to be funny? People on Slashdot actually believe this load of bullshit?
UUID for disks folded into systemd? systemd crowd (developers?) are windows devs? sysadmins don't reboot servers?
If that's the "knowledge" of the new wave of Linux users, I guess old Linux sysadmins won't have to fear for their jobs.
Essentially it's being bundle in with other services.
That's the only truth in this post till now.
Sadly, SystemD is not well tested enough for most people running linux on a server to trust it especially since the guy who wrote it wrote PulseAudio and people are still having issues related to that piece of shit.
Another lie. The main problem of systemd is that there's so much to do given the state of Linux init systems, that it's still a fast moving target, too fast for distros. It will stabilise when most of the features are implemented.
* Boots fast
* When it breaks, you're fucked
* Obsoletes 20-30 years of accepted best practices and knowledge of how to use linux tools
* No real new features
* Is network connected and running as superuser
* Is unaudited
* Is virtually untested
* Was written by a raging moron
* Is completely unneeded by a large section of people who have run linux for a long time
Essentially, it's the Windows 8 of the *nix world
This shows a lot of ignorance on even how a Unix like system works. Init is launched by the kernel, so of course it runs as super user, and no, it's not network connected, not PID 1 at least. The rest is drivel or nonsense, like it obsoletes 20-30 years of best practices and knowledge, this makes no sense, I can operate my servers with best practices that I couldn't use with sysvinit, and I still use the linux (you mean GNU?) tools the same with systemd.
Executables configuration scripts (init scripts) are not at all best practice, even less when they use configuration files of their own, scattered in several different files, and whose behaviour can be modified by the environment, making for a huge attack surface that can go undetected. That's what you call best practices? And calling people names doesn't make your argument any better.