Messages in this thread | | | Date | Fri, 28 Apr 2006 15:03:23 +0100 | From | Paulo Marques <> | Subject | Re: checklist (Re: 2.6.17-rc2-mm1) |
| |
Martin Bligh wrote: >>[...] > I don't want to boot it, as that gets into security nightmares, but I > should be able to provide something that does static testing.
Actually, booting might not be that bad using a virtual machine with qemu.
You can use a command like:
qemu -nographic -kernel <kernel_image> -append <command line> -initrd <initrd file>
and then set up the <command line> to use the serial console, and the initrd to something simple that just outputs "[SUCCESS]" and powers off.
You can then monitor the standard output of this process. If after a minute (for instance) no "[SUCCESS]" appears on its standard output, it didn't boot and you have the dmesg data to (hopefully) show why it didn't boot.
If it outputs "[SUCCESS]", then it booted fine. You still can append the dmesg output to the test report.
Of course, the kernel configuration must include support for serial console and the initrd filesystem used, at least.
Well, just my 2 cents,
-- Paulo Marques - www.grupopie.com
Pointy-Haired Boss: I don't see anything that could stand in our way. Dilbert: Sanity? Reality? The laws of physics? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |