Starting from 2.6.8 kernel sources, the bootsplash patch has been subsided by fbsplash from http://dev.gentoo.org/~spock. Since the gensplash project is going to be the default for next releases, there should be a way to generate patched initrds automatically also with genkernel, maybe with a --gensplash=theme option (that should imply --no-bootsplash), and an option in genkernel.conf. Or it could detect if the kernel version was patched with fbsplash or not, and then choose to generate the right initrd (a worse solution, imho).
I'm adding livecd@ because at this time we will either be sticking with a 2.6.7 kernel, or not having any splash screens on our next release. While I would be perfectly fine with this, I'm sure many of our users would complain about the sudden loss of eye-candy.
Tim? Help! We're running out of time on this. If you don't think it'll make it by Friday, then let me know.
Alright... what we need is a --fbsplash option that runs the splash_geninitramfs and puts it into the proper location added to genkernel. The --fbsplash option should of course imply --no-bootsplash (as --bootsplash should imply a --no-fbsplash) to keep genkernel from trying to bring in a bootsplash theme. Why? Because splashutils requires a fully-configured kernel to build. This means we cannot run the splash_geninitramfs before running genkernel, and we obviously cannot run it after genkernel.
Created attachment 41800 [details, diff] gensplash patch or --gensplash will do... I am testing this patch now, so we'll see if it works. It was patched against CVS.
Only issue I can see is /usr/src/linux being hardcoded: the --kerneldir can set an arbitrary kernel directory. Other than that, patch looks fine, so if it works then I'll happily commit it in for you.
Created attachment 41816 [details, diff] gensplash patch part deux OK. I moved the gensplash stuff until after the callback stuff, since it has to be brought in via callback at least when used with catalyst (yay gensplash!) and I changed the hard-coded /usr/src/linux to use ${KERNEL_DIR} instead.
Yeah... so those patches didn't work since gensplash was apparently more complex than I thought... anyway... plasmaroo has a working patch now and we'll be releasing a new genkernel shortly once we iron out one or two other bugs.
