Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for June 20, 2013
Pencil, Pencil, and Pencil
Dividing the Linux desktop
LWN.net Weekly Edition for June 13, 2013
A report from pgCon 2013
We could fix the BIOS too, given the chance. It shouldn't be exempt.
Don't cheat on boot time.
Posted Nov 26, 2009 7:47 UTC (Thu) by Los__D (guest, #15263)
Didn't cheat on boot time.
Posted Nov 26, 2009 12:13 UTC (Thu) by kragil (guest, #34373)
27 seconds is nothing special, my pretty default Kubuntu install on my EeePC 901 takes 28 seconds. So 27 is bad for a custom install IMO.
And this also shows how great the 7 seconds ChromeOS needs to login are.
Posted Nov 26, 2009 8:50 UTC (Thu) by Tuxie (guest, #47191)
Posted Nov 26, 2009 10:46 UTC (Thu) by dwmw2 (subscriber, #2063)
To exclude those and publish just an irrelevant microbenchmark of the part I want you to think about would be massively disingenuous.
If boot time matters a lot, that will definitely affect the choice of operating system I run it on. It could also affect my choice of chipset/CPU — if I really care about how quickly the whole thing starts up, I'm more likely to use hardware from a company which supports open source projects like coreboot, rather than one which refuses to support open source and leaves me stuck with a slow, closed-source BIOS implementation that I can't fix for myself.
Posted Nov 26, 2009 10:57 UTC (Thu) by Tuxie (guest, #47191)
If he was reviewing a netbook with Moblin preinstalled, of course the BIOS time should be counted, but that was not the case here.
Posted Nov 26, 2009 20:00 UTC (Thu) by amikins (guest, #451)
Posted Nov 26, 2009 21:32 UTC (Thu) by Tuxie (guest, #47191)
Posted Nov 26, 2009 23:29 UTC (Thu) by giraffedata (subscriber, #1954)
And it doesn't matter. Readers aren't trying to judge the engineering effort; they're judging the result. If Moblin can't make boot fast because the time is spent in things Moblin can't control, then Moblin fails just as surely as if Moblin engineers just did stupid things in the code.
Another way of putting it is that to the extent that things outside Moblin elongate the boot, the time it takes Moblin per se to start is irrelevant and the article might as well not mention it.
Posted Dec 3, 2009 12:16 UTC (Thu) by robbe (guest, #16131)
I'd expect the BIOS time to be below 10 seconds in this case, so trimming
down the 27 second part is very relevant.
FWIW, which hardware vendors support coreboot well?
Datapoint: one of my *server* VMs takes 26 seconds from poweron to login.
P.S.: Am I the only one who thought that our editor was surfing a site
named "Rate Wives" -- until I got that it was the logo of a popular TV
show cut off? Another case of screen too narrow...
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds