I guess some of you already saw this, but for the rest of you, it's a really good example of what some inventive low-level optimization (and the cutting-away of unnecessary parts of apps/executables) can do to a system's responsiveness.

Reduction of combined boot-time and GUI application start-up to only 1 second!

Video:
http://www.embedded-bits.co.uk/2011/1-second-linux-boot-to-qt/

Slides with details:
http://www.slideshare.net/andrewmurraympc/elce-the

then that is exactly GUI application start-up, but not a SYSTEM start-up.

The camera is a device run by the hardware,its not solely a GUI boot, its just a boot with all the other trimmings removed.

I'm not completely sure what any of you mean, but it is a (downstripped) Linux system, booting from scratch (including having its power cord pulled) and then also starting a GUI application, all in one second.

Which part of that is hard to understand?

I have a friend that showed me a very short boot time (reaching login screen) on Kubuntu. Part of the trick was that he used a solid-state disk.
Obviously it's unlikely that there is a hard drive on that renesas board so I was wondering if not that OS is booted from a flash? that could maybe play a role....

Sure, but before their optimization, the boot-time from the same flash was > 19 seconds, and afterwards it was 0.77 seconds, so it seems that their other optimizations played the key role there. (all details are in the slides linked above)

sorry, my replay was itself "extraoptimized".
i meant following: that 'trunked-OS' is capable to DO-ONLY that one GuiApp.
nothing more big it can do..

That's brilliant indeed.