Slashdot Mirror
Software Tweak Makes Linux Boot In Under 200 ms
An anonymous reader writes "A version of Linux has been created that radically speeds up system boot time -- to less than 200 milliseconds (ms) from power-up to application code startup. The techniques, created by Real-time Linux vendor FSMLabs, are processor independent, and boot times of under 100 mS are expected in the future." Update: 09/30 01:04 GMT by T : Yep -- both headline and post should have read "ms" (milliseconds) rather than "mS" (milli Siemens); thanks to all the alert readers.
any linux user wants to sacrifice their uptime to boot faster
alias uptime="echo '5:33pm up 22342352324 days, 6:28, 2124315623 users, load average: 2432.40, 12312.31, 123123.19'"
when linux boots 200 mS before I turn the computer on.
Linux doesn't crash. It "creatively parks".
I have something in common with Stephen Hawking...
// Code to make Linux startup look like it's doing something
// Insert in a few hundred random places
long foo = 0;
while (foo < 10000000)
{
foo++;
}
...
"...speeds up system boot time to less than 200ms... The techniques are processor independent"
Could anyone think about the 386SX/20 please???
Scene one, Act One
:(
Adrian Lamo in a orange prison jump suit conferencing wit his attorney.
Ring Ring
Attorney: Hold on Adrian, I have to take this call. (talking into cellphone) Yeah.. ok... Great! ok..Thanks!
Great news Adrian!
Adrian: (curious/happy): What?!
Attorney: I just saved 4.8 seconds on my Linux boot time with FSMLabs!
Adrian:
I had a professor tell us this story of one of his previous coworkers:
She had designed and implemented a simple service on top of unix which was accessed by a moderate number of users. When the time to put it into production came, she looked at her remaining few crashing bugs and determined to put in a monitoring loop that would reboot the server if such a situation happened. She also determined that no data loss would occur.
Why did she do this workaround, and how did she determine what bugs she could leave in?
She had a 5 digit company phone extension. She determined that someone could call her, if she let her phone ring twice, in a short period of time. During this time the server would have finished rebooting and start serving again. She could answer the call and simply say, "Try it again", whereupon the user would find that his operation worked this time.
So remember - if your server can reboot itself (and does so automatically and safely) before they can finish dialing tech support, you have no worries!
-Adam
Actually, the "S" unit refers to the Imperial Second, which is defined as the interval of time between now... and now.
I disabled a lot of stuff that autolaunches, like virus scanners, firewall, etc
Good idea. Virus scanners and firewalls use WAY too much overhead. Heck I used to run them and they interfered with my screen savers and stuff. Who needs em.
Load average of 123123.19?! Holy crap. I'd rather it look like this:
5:33pm up 22342352324 days, 6:28, 2124315623 users, load average: 0.01, 0.00, 0.00
The uber-server.
It's too bad the damn power companies havn't spent some time improving their boot times... it took them like a week to restore my power *grumble*
This is VERY easy to do
Um...yeah.
I visited your links and it all immediately became blindingly clear to me...
daemontools and svok...
Yep.
> the last time I tried to suspend the armada
The last time we tried to suspend the Armada, all our ships sank.
What I want to know is how Windows detected here that "Kernel32 is not responding"... Maybe Kernel32 is not the REAL kernel? :) Maybe their is a shodowy overlord kernel who's really running the show (perhaps a linux kernel?) :)
ovit
hard core geek-ware