![]() | ||||||||||
Messages in this thread |
Hi! > > Your best bet would be to use a system that already implements some > > form of checkpointing or process migration, and use this to > > preserve user space state across kexec reboots. openMosix may be > > [snip] > > preserving user state would not be so much the problem as would > the various internal kernel data structures (vm stuff, dcache, etc.) Actually, you want to kill vm structures, dcache etc. You only want userspace-visible state to be carried forward to minimize possibility of bringing bugs to new kernel. Pavel -- Worst form of spam? Adding advertisment signatures ala sourceforge.net. What goes next? Inserting advertisment *into* email? - 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/ | |||||||||
| Last update: 2005-03-22 12:31 [from the cache] ©2003-2008 | ||||||||||