On Thu, Mar 5, 2009 at 3:11 PM, <pgf(a)laptop.org> wrote:
now that it's been pointed out that most of the cat processes
were from bootchart itself, i highly doubt there will be
Heisenbug :-) even then, it does give you fairly good idea of what's
up during boot.
SoaS is meant to run on any hw out there, and a lot of the
optimisations on the XO are because we _know_ what hw we have. Does it
make sense to get "skip all this hw poking if it looks like an XO"
patch upstream?
In fact, this might be something that upstream wants to think about in
a generic sense. All the boot-in-5s focus lately is a lot of fun (and
great for end-users, I surely want _my_ boxes to boot in 5s), but
depends in part on skipping a lot of poking and waiting for hardware.
Anyone building a custom Fedora for a netbook will want the same thing
we want: a way to declare a "fast path" for known hw. Specially on the
netbook segment this can have a huge payoff. (Wonder if Ubuntu doing
something like this?)
cheers,
m
--
martin.langhoff(a)gmail.com
martin(a)laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
-
http://wiki.laptop.org/go/User:Martinlanghoff