Controversy is nothing new when it comes to systemd. Many people find this new Linux init system to be inherently flawed in most ways, yet it is still gaining traction with major distros like Arch Linux, openSUSE, Fedora, and soon both Ubuntu and Debian GNU/Linux. The adoption of systemd for Debian 8 "Jessie" has been particularly fraught with strife and animosity.
Some have described the systemd adoption process as having been a "coup", while others are vowing to stick with Debian 7 as long as possible before moving to another distro. Others are so upset by what they see as a complete betrayal of the Debian and open source communities that there is serious discussion about forking Debian. Regardless of one's stance toward systemd, it cannot be argued that it has become one of the most divisive and disruptive changes in the long history of the Debian project, threatening to destroy both the project and the community that has built up around it.
(Score: 2) by cafebabe on Sunday September 28 2014, @05:38PM
So, in that example, a server with 64GB takes 309 seconds to boot. 137 seconds is for the memory test. That's about 0.5GB/s. But, hey, after you've diagnosed conflicts, systemd will reduce that by about 0.5 seconds.
1702845791×2
(Score: 2) by E_NOENT on Sunday September 28 2014, @07:44PM
I agree.
The whole "faster boot times" schtick is pretty meaningless IMHO.
I'm not in the business... I *am* the business.
(Score: 2) by cafebabe on Sunday September 28 2014, @07:51PM
The claim of faster boot times is worse than meaningless. It demonstrates a lack of understanding of typical requirements and it demonstrates a lack of understanding of Amdahl's law [wikipedia.org].
1702845791×2