Werner Almesberger <[EMAIL PROTECTED]> writes: > So if there was a vote to be cast for getting kexec into mainline > as quickly as possible, you'd certainly have mine :-)
The hard one there is support of arbitrary OS's. Most of the existing interfaces that have been designed require callbacks during booting which is the hard piece to support in a linux based environment. But loadlin does fairly strongly show that you can do interesting things to load a non-native OS if you have the appropriate environment. I think part of the challenge is the conversation on what should happen with bootloaders is fragmented. But that may not be a bad thing. Most people want to implement simple boot policies, and really don't care for the full complexity that some firmware solutions allow. So what I have seen is people will take kexec and implement their custom policy instead of doing something complex. With 1MB ROMS starting to show up it using a kernel based bootloader is starting to look like a real possibility on the LinuxBIOS front. There is also the other use case that I have a use for as well. Kernel upgrades. I need to get my patch into /sbin/reboot or at least the initscripts but the ability to easily switch from one kernel to another without going through the firmware is also very handy. That case is the core case has been my motivating factor lately. And at this point the question is really not about getting kexec into the mainline. Andrew picking it up, the syscall number being reserved, and interface being fixed have done that. The goal now is to build enough confidence so that we can move from the development to the stable kernel. Want to help? Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
