I run my Sheeva rootfs from the internal NAND, and if I have a kernel with this, I can use iotop to see where the majority of my file writing is occuring. (A good way to increase the life of my flash, and/or improve performance by relocating to faster media).

If this isn't a great idea for mainstream kernels, can I suggest a "specials" directory in sheeva-with-linux for one off testing stuff. (Clearly things are robust enough now they wouldn't have to be maintained every release).

Lastly, many thanks cxbiker, your kernel builds are awesome, and it means we don't need compiler enviroments on our plugs, or opening up to the world of hurt that is cross-compiling..

I run my Sheeva rootfs from the internal NAND, and if I have a kernel with this, I can use iotop to see where the majority of my file writing is occuring. (A good way to increase the life of my flash, and/or improve performance by relocating to faster media).

If this isn't a great idea for mainstream kernels, can I suggest a "specials" directory in sheeva-with-linux for one off testing stuff. (Clearly things are robust enough now they wouldn't have to be maintained every release).

Lastly, many thanks cxbiker, your kernel builds are awesome, and it means we don't need compiler enviroments on our plugs, or opening up to the world of hurt that is cross-compiling..

Well I don't think the overhead that would go along with enabling those options justifies placing it in the standard kernel. But as you suggest, I don't see a problem with creating a /testing directory for "special" testing versions. After I figure out how I want to maintain a testing tree I'll get something uploaded there for you. I'm busy working on other stuff, so it'll probably be a day or so.