Linked by Hadrien Grasland on Fri 14th Jan 2011 14:53 UTC, submitted by quickie
Linux "At the end of last year, to demonstrate my company's swiftBoot service, I put together a rather impressive demo. Using a Renesas MS7724 development board I was able to achieve a one second cold Linux boot to a Qt application. Here's the demo."
Order by: Score:
Old news?
by Timmmm on Fri 14th Jan 2011 16:08 UTC
Member since:

Didn't you guys cover this when it happened in September?

Reply Score: 2

RE: Old news?
by vodoomoth on Fri 14th Jan 2011 16:20 UTC in reply to "Old news?"
vodoomoth Member since:

Then I must have missed it, I don't remember having seen the news item.

Reply Score: 2

RE: Old news?
by Neolander on Fri 14th Jan 2011 16:40 UTC in reply to "Old news?"
Neolander Member since:

EDIT : Nevermind

Edited 2011-01-14 16:41 UTC

Reply Score: 1

by vivainio on Fri 14th Jan 2011 18:38 UTC
Member since:

Qt Embedded a bit "last year". The really exciting stuff is the "Lighthouse" project, that allows Qt to run pretty much everywhere, fast - adaptation to graphics systems is done by plugins, which are relatively easy to create.

As an example, a lone hacker was able to make Qt run on Android using Lighthouse. Lighthouse is also the way Qt will run on Wayland.

Lighthouse will be officially released with Qt 4.8.

Reply Score: 5

by Elv13 on Fri 14th Jan 2011 20:51 UTC
Member since:

I spend some time too doing that. I can down to 7 second to full boot and 10 to X on a 5400rpm hard drive. Using xfbdev was a bit faster to boot and Qt performances were good, but GTK apps fail to run at decent speed. To get that:

-I start useless services after complete boot,
-Rely on precisely timed disk prefetch
-Avoid IOwait
-Use scripts until some daemon are fully loaded (like parsing dmesg and use mknod to do udev job until the boot process is over, as udev is the slowest of them all.
-Replace startx with sometinng lighter (loop+wait 0.01 until it is ready to start the WM
-Use a faster but still as flexible as KDE WM like the (great) AwesomeWM
-Never spend time without IO, start to load Qt and KDElibs as soon as evertthing else is in the cache.
-Strip down the kernel to a monolithic binary (no module, drop the router stack and all uneeded stuff enabled by default)
-Use -Os for all packets when compiling
-Replace Bash with Dash for the root use
-Replace the DM (KDM/GDM) with a C program that:
--->Swtich the SUID/GUID to the corect user (auto login)
--->create the necessary env vars and create a process shell
--->fork1 wait 10 second to create the getty (CTRL+F1,F2, etc)
--->fork0 launch the new startX script
--->fork1 start the other services and load the missing modules like wifi.
-Drop runlevel and manage them manualy (no inittab)
-Be quiet, print as little as possible, printing on framebuffer is slow and lock everything in IOwait mode.
-Drop services dependency tracking (be smart here)
-Start everything in parallel as long as it make sense
-Use as little command as possible
-Remove the #!/bin/bash where it should be #!/bin/sh

Edited 2011-01-14 20:53 UTC

Reply Score: 6

by bebop on Sat 15th Jan 2011 00:56 UTC
Member since:

I got Haiku to boot in around 7 seconds as well. To get that I did:

- Install Haiku onto a partition.
- Boot the OS

On a serious note, the slides that are linked on the site are a pretty interesting read.

Edited 2011-01-15 00:57 UTC

Reply Score: 8

RE: Haiku
by Earl Colby pottinger on Sat 15th Jan 2011 04:01 UTC in reply to "Haiku"
Earl Colby pottinger Member since:

Install onto a SSD and booting Haiku-OS drops to less than 5 seconds on 1.67GHz Netbook.

Edited 2011-01-15 04:03 UTC

Reply Score: 4

RE: Haiku
by TQH ! on Sat 15th Jan 2011 17:06 UTC in reply to "Haiku"
TQH ! Member since:

Yeah, we are still slow. We should turn down the logging and optimize a few things, but atm we want the info from the logs. ;)

Reply Score: 1

1-2 minutes
by fretinator on Sat 15th Jan 2011 02:00 UTC
Member since:

Is the required amount for a trip to the coffee pot. Please don't boot faster than that, thank you.

Reply Score: 6

560 milliseconds from reset to shell
by constantine on Sun 16th Jan 2011 23:33 UTC
Member since:

on 300 MHz ARM, NAND flash:

Reply Score: 1