Stuff Michael Meeks is doing
|
|
This is my (in)activity log. You might like to visit my employer
Novell which is an amazing company, and also
Dell who in days of yore provided me with a
free laptop for Gnome development / conferences.
Also if you have the time to read this sort of stuff you could enlighten
yourself by going to Unraveling Wittgenstein's net or if
you are feeling objectionable perhaps here.
Older items:
2009: (
J
F
),
2008: (
J
F
M
A
M
J
J
A
S
O
N
D
),
2007: (
J
F
M
A
M
J
J
A
S
O
N
D
),
2006,
2005,
2004,
2003,
2002,
2001,
2000,
1999,
legacy html
-
It seems that Miriam has
started writing a blog from Kabul - and very well written it is too.
Looking forward to seeing the great work that Hagar does applied there.
-
Played with pybootchartgui some more; with the new high res
bootchart collector, we start to see some fun problems: eg. when we
do a double fork to spawn a process - we sometimes catch that process
and assign eg. 'boot' a parent of the (very transient) parent - which
appears to ruin the clean ordering.
-
The result of adding Arjan's nice kernel dmesg parsing scheme to
bootchart, of course converted from perl to python, and albeit in a hacky
way so far is:
Of course, it is less colourful, and less detailed than the
scripts/bootchart.pl output - but hopefully will show up
any particularly glaringly slow bits. Now to find out / and or render
why there is such a long gap between the kernel appearing to finish,
and init starting to spawn things.
-
Worked with Matt on grub pieces. Amused by Matt Assay's Linux is
bloated comment; to me - the worst of the bloat would be around
hack-ability. It is one (saneish) thing not to freeze your internal APIs
forever - it is -very-much-something-else- to insist that all people trying
to build, package and test the kernel need to join in with the 'measuring'
contest of how quickly (or not) they can build the whole thing. If I need
to only change ten lines of code, why do they force me to compile 10 million ?
Sure - if I am already a kernel hacker, I can do that easily - if I am not,
life is sufficiently hard to keep people away from simple hacks. I'd love to
see a kernel that can be build straight through, and yet is routinely
packaged and built as a dozen separate source (subsystem?) packages - of
course whatever static library intermediates are lame, but - so is excessive
build pain.
In case it's not painfully obvious: the reflections reflected here are my
own; mine, all mine ! and don't reflect the views of Novell, The
Lithuanian Gov't or Arnold Schwarzenegger. It's also important to
realise that I'm not in on the Swedish Conspiracy.
Occasionally people ask for formal photos for conferences,
bio.
or fun.
Michael Meeks (michael.meeks@novell.com)
