SoylentNews is people
SoylentNews
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: 4, Interesting) by VLM on Sunday September 28 2014, @11:32AM
For reasons very on topic to this article discussion, I installed freebsd 10.0 on Friday and started working on my recipes to integrate it with everything else.
The default boot loader for freebsd pauses for 10 seconds asking if I wanna go normal/multiuser or singleuser/rescue or whatever other options. The rest of the boot takes less time than that bootloader pause.
There's some heavy propaganda that its impossible to boot quickly without systemd but freebsd is pretty snappy, and it wastes most of its time in POST and bootloader anyway.
Another weird problem I've observed is xorg and friends take longer than the rest of the system.
So its like 10 seconds to post, 10 seconds for the boot loader, system boots in like 5 seconds, X takes maybe 10 seconds. Then LDAP and AFS (or maybe kerberos?) are unhappy for perhaps the first 3 minutes or so, such that I can't log in. If I could magically lower my system boot time to zero it would only improve boot times by about 3%. And the improvement isn't going to be that great and the pain isn't going to be worth it (very gentoo)
And this is on a desktop with all kinds of stuff running. The servers usually only have one service, so "mysql", thats it, so they boot even faster.
(Score: 0) by Anonymous Coward on Monday September 29 2014, @04:48PM
Are fscks, scsi device enumeration, and more recently: udev(systemd?) hanging the system for 30 seconds over whatever that module 'issue' was that Lennart complained to Linus about. The only other one has been ubuntu hanging for 60 seconds on network bringup for devices that aren't in the system (I've migrated HDDs between systems pretty regularly, either due to upgrades, to save time rearranging hardware, or just curiousity.) In that regard I haven't found a good way to either purge old network configs, or at least get it to ignore them for a faster bootup. Given that these systems are up for weeks/months at a time on average it hasn't been a major deal however. And in that regard system falls flat regarding benefits versus complexity. Most all of the plug and play features offered by systemd were already available from other sources. Most of them worked in a transparent fashion (Save maybe using Thunar or E17 for removable drive mounting instead of gnome/systemd.. do both of those use gvfs as their backend?)