> > Systemd is > > larger than init, so for embedded it may well quadruple boot time. > > What utter bullshit. Please, Kevin, if you are going to throw around > numbers, do some measurements first. You keep picking on other subjects too at one tiny part without considering all that I have said. /sbin/init 32K actually larger than I thought considering it's job was designed so tightly bound. /bin/systemd > 800K (26 times as large) I have an embedded board sitting right here that can run Linux and has 64K of SRAM by default. As I have said you are talking about Linux systems that are nearer the top smaller end of the embedded and actually my Android probably takes longer to boot than my desktop, maybe when I get time as Sony aren't providing updates as they promised I will mod cyanogen to boot a bit quicker or stop it slowing down further if systemd lands with a simple init. My real point was that the systemd speed argument was pointless and the bloated argument in violation of UNIX principles wasn't. There is nothing stopping building concurrency on top of init like Upstart which obviously has major issues. Do you have any numbers on how much time it saves you. I know Gnome takes many many times longer to load than systemd saves! -- ________________________________________________________ Why not do something good every day and install BOINC. ________________________________________________________
