3 ms·
There are embedded Linux demos that boot into a GUI application in about a second. Linux systems don't boot slowly because "POSIX" isn't capable, it is a matte
by ahartmetz 7y ago
There are embedded Linux demos that boot into a GUI application in about a second. Linux systems don't boot slowly because "POSIX" isn't capable, it is a matter of boot time vs. flexibility and developer convenience / development time. There are also Windows CE systems that boot that fast. Linux demo: https://www.toradex.com/de/videos/fast-boot-demo-with-linux-and-qt https://www.toradex.com/de/videos/fast-boot-demo-with-linux-...
I have a few moderate boot time improvement projects on embedded Linux under my belt. The typical low hanging fruit are hardcoded wait times in boot loader and drivers, unnecessary drivers, unnecessary features (did you know that PPP - yes, the modem thing - support takes a while to initialize?), slow to mount filesystems, bad choice of storing / compressing the kernel, and delays in the init system (run the application as soon as possible instead). More hardcore techniques are various methods to reduce dynamic linker overhead and reordering blocks on storage in the order they will be read at startup.
- planteen 7y agoCame here to say this. I've worked on embedded Linux projects with a boot time requirement of 2 seconds and easily made it. I guess part of the difference is that you explicitly enumerate all hardware and drivers in a device tree on embedded rather than figuring it out on the fly like on a desktop/server machine.