Ok, I'm confused.
The midori FAQs and docs talk about rebuilding taking a specific linux distro and 1.5G of hard drive space.
If we just want to update the kernel (for instance, I need usb audio) or add truetype fonts or something, do we have to do all of that, or can we just add pieces to the build kit and go?
I tried the latter, by sticking my own kernel on there (from another, jail-bait based install on the IA1) and it failed. Now I understand why, mostly. I didn't have the i2o stuff in my kernel, and the midorit patches weren't there. (Where are those patches?)
It seems like someone (maybe me) should get a "current" linux src tree, do a 'make oldconfig' based on the midori config and see if it works. Has anyone tried this already?
If we DO want to rebuild a kernel, assuming that we CAN'T use a "current" kernel, but instead use the 2.4.6-midori kernel, can we build that in the traditional way, or does it have some kind of funky build process?
I mean the usual...
make xconfig (or whatever)
And, I noticed that there is only one module in /lib/modules... is that for a good reason? Should we NOT use modules, but use compiled-into-kernel stuff instead?
Sorry about all of these questions; the notes on midori.transmeta.com are a little light.