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.
I have noticed that *nix boot times are noticibly longer than Windows XP boot times. I have never been able to figure out why this is - does anybody know?
Thanks
John
...And when they came for me, there was no one left to speak out for me." - Martin Niemoeller (1892-1984)
The article says this work was done to improve the boot time of embedded devices, but I don't see anywhere why these changes couldn't be applied to any other computers running linux.
"Prefiero morir de pie que vivir siempre arrodillado!"
So, this is a good improvement it seems, but shaves away 4.5 seconds or so out of maybe 30 sconds or over a minute for many people.
True, but this is still great.
The article says, "less than 200 milliseconds (mS) from power-up to application code startup." The thing that makes this great is that not every device is going to go through the entire *nix init sequence.
How about a device like a Linux embedded router, or something like that? Just a kernel running and that's all. Or how about a dashboard mp3 player that only needs to run one application?
This makes Linux much more like customized firmware, and there are plenty of places to use that.
Granted, this'll be great when it makes it to the desktop, too. =)
Weaselmancer
Weaselmancer
rediculous.
Of course, DOS with edit.com, or an early version of wordperfect or wordstar would put everything else to shame
What a misleading article.
Could've at least put non x86 or embedded device in the title.
We have secretly replaced these Slashdot mods' sense of humor with a rusty nail. Let's see if they notice!!
... that when a company doesn't put its kernel changes out immediately, there's calls for hanging them for violating the GPL, but when a linux company optimizes boot-up routines in the kernel, nobody is asking when the patches are going to be making it into the mainline kernel?
from the looks of the article, FSMLabs has been basically profiling the kernel, looking for sticking points, and optimizing them.
why wouldn't at least some of this work be contributed back to the mainline kernel? it is modifications on a GPL'd kernel, after all.
Well just remember these are for imbedded devices. Where Uptime is not much of an issue. A lot of these things are running on battery, so if you get 3 days of uptime that is absolutely grate because the wonderful battery life. For these devices boot speed is very important imagine a Palm pilot having to boot up normal linux when you turn it on. Oh your batteries would be dead before sendmail realized that there is no network configured on the system.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
For servers a big draw back is that if you have to patch the kernel (or update it) you must reboot, but if the acual reboot only takes less than a second, users might hardly notice the downtime (you could reboot and keep a 99.99% uptime).
Why would an embedded device need a firewall or virusscanner if it takes no input but from a certified source?
Real men measure uptime as a percentage, not as an absolute value.
This is your sig. There are thousands more, but this one is yours.