News for hackers. Stuff that matters.
Re:Systemd: The Biggest Fallacies by zimbatm on Saturday September 27, 2014 @02:14PM (#8377737)
That's for desktops where boot times are more important. Starting A and B at the same time allows to lower that time.

On servers you want to wait for A to be ready before starting B. Otherwise the socket min timeout from B to A is dictated by the startup time of A and not the normal runtime timeout (seconds vs millis).

Re:Systemd: The Biggest Fallacies by dnr on Saturday September 27, 2014 @04:19PM (#8378073)
In my recent experience, server boot time is more important to me than desktop boot time. My desktop and laptop basically never boot anymore, they just suspend and resume. But I wait for ec2 instances to boot at least several times a week.
Re:Systemd: The Biggest Fallacies by zimbatm on Sunday September 28, 2014 @08:14AM (#8379540)
Most of the EC2 boot time is taken by the resource allocation and provisioning of the host (~2min). Changing the init system would only save you a couple of seconds of that.
Re:Systemd: The Biggest Fallacies by digi_owl on Saturday September 27, 2014 @08:43PM (#8378597)
Giving me further proof that the "shism" is between traditional server admins and cloud admins.
Re:Systemd: The Biggest Fallacies by zimbatm on Monday September 29, 2014 @03:16PM (#8384649)
Except that I am a cloud admin