"achieving a level of previously unmatched performance on any embedded Linux."
Wrong Goal and also factually incorrect. uClinux has been booting on industrial controllers in
under 1 second to functional, completely running state for 10 years. And on processors running
very low double digit MHz clock speeds (and yes, from Motorola, now Freescale too). The key is not
so much replacing init with a single purpose application (that can help), but making a proper tiny
stack that does just what you need, of which init is a part. Thankfully, just what you need is not so
different as one might initially think from application to application.
If you need to do "tuning of the entire software stack" then you're using the wrong stack.
Posted Jul 14, 2009 21:29 UTC (Tue) by BrucePerens (subscriber, #2510)
[Link]
Busybox got to the prompt really quickly back when I wrote it in '96. Most of the time spent in booting back then was waiting for the kernel to not detect devices.
Wrong "stack"
Posted Jul 14, 2009 21:37 UTC (Tue) by arjan (subscriber, #36785)
[Link]
the kernel has been fixed since; typical is around 0.6 seconds for a kernel boot with all drivers in there....