Re:What should we expect from a modern init system?
by hactually on Monday January 20, 2014 @03:52PM
(#7091671)
Propaganda? Jeez.
sysvinit is long overdue retirement - I've worked with it for many years can't wait for it to die.
It can't handle power management, it calls out to a multitude of scripts/external applications just to stop start and restart (oh, and which command options are the correct ones to support?), it can't manage processes through their lifecycle.
People constantly trot out that it's not the unix way... Linux is not unix. X is going away next, are you going to fight to keep that all the way too?
Also, why use external tools to analyse the bootup?
$ systemd-analyze
Startup finished in 785ms (kernel) + 395ms (initrd) + 2.184s (userspace) = 3.366s
$ systemd-analyze plot > file.svg
sysvinit is long overdue retirement - I've worked with it for many years can't wait for it to die.
It can't handle power management, it calls out to a multitude of scripts/external applications just to stop start and restart (oh, and which command options are the correct ones to support?), it can't manage processes through their lifecycle.
People constantly trot out that it's not the unix way... Linux is not unix. X is going away next, are you going to fight to keep that all the way too?
Also, why use external tools to analyse the bootup? $ systemd-analyze Startup finished in 785ms (kernel) + 395ms (initrd) + 2.184s (userspace) = 3.366s $ systemd-analyze plot > file.svg