Eric W. Biederman wrote: > The hard one there is support of arbitrary OS's.
Bah, couldn't care less :-) If all else fails, you can fall back to the "old-style" boot loader, and let this one boot the legacy OS. (Well, for GRUB, you'd need the fallback extension, if this isn't a standard feature yet.) > 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. I think many of them would just be as happy with a more complex solution, as long as it comes in a nice bundle. Of course, if there is no nice package to start from, they'll only implement the bare minimum. Also, in most cases, we can probably ignore space issues for now, leave some room for experiments, and optimize later. > The goal > now is to build enough confidence so that we can move from the > development to the stable kernel. Yes, that's what I mean with it being in "mainline". For user space to begin making use of kexec, it really should be part of a kernel most people can accept for regular use. > Want to help? Trying to, by explaining why it should move on :-) Anything else you need ? - Werner -- _________________________________________________________________________ / Werner Almesberger, Buenos Aires, Argentina [EMAIL PROTECTED] / /_http://www.almesberger.net/____________________________________________/ - 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/
