| |||||||||||||
|
| |||||||||||||
Don't cheat on boot time.Don't cheat on boot time.Posted Nov 26, 2009 10:57 UTC (Thu) by Tuxie (guest, #47191)In reply to: Don't cheat on boot time. by dwmw2 Parent article: The Grumpy Editor's Moblin review
But this review was a review of Moblin, not the laptop it was running on.
If he was reviewing a netbook with Moblin preinstalled, of course the BIOS time should be counted, but that was not the case here.
(Log in to post comments)
Don't cheat on boot time. Posted Nov 26, 2009 20:00 UTC (Thu) by amikins (guest, #451) [Link]
To be fair, it WAS a netbook with Moblin preinstalled. :)
Don't cheat on boot time. Posted Nov 26, 2009 21:32 UTC (Thu) by Tuxie (guest, #47191) [Link]
Ouch, you're right. If someone asks for me, I'm over there in the corner hiding for a while.
Don't cheat on boot time. Posted Nov 26, 2009 23:29 UTC (Thu) by giraffedata (subscriber, #1954) [Link] I don't think it was a review of the whole package, even though the first tests were done on a the preassembled package. It was a review of Moblin.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.
|
|
||||||||||||