On Thu, Jan 22, 2015 at 1:36 PM, Tom H <tomh0...@gmail.com> wrote: > > I'm also curious about the future ChromeOS init. Upstart is, sadly, > walking dead (IIUC Ubuntu'll stop using it in 2019 once 14.04 is > EOLd). It's going to be systemd or Android init, isn't it? AIUI Google > wants to have Android and ChromeOS converge somewhat so it's more > likely to be Android init. Speculation! :) >
Interesting, I hadn't thought about Android init. Neither ChromeOS nor Android support user-supplied daemons or anything else traditional along those lines (anything running in the background is run at a higher level in the framework). However, I think a key difference here is suspend/hibernate. Android doesn't do that, and ChromeOS does. Android goes into lower-power mode all the time, but I don't think that is the same as a traditional desktop sleep mode, and Android definitely doesn't do suspend-to-disk. ChromeOS tends to hide this stuff from the user, but I believe it does both. That seems likely to greatly favor an event-driven init, though the fact that you aren't running tons of arbitrary daemons might help to mitigate that need. -- Rich
