Other uses could be as a recovery method after some sort of system crash
or problem or solution which requires a reboot.
The main problem that comes to mind is all the absolute resources the
kernel manages that may not be available when the process comes back.
Two options come to mind off-hand: (1) just wait until that resource
becomes available again, getting in line for that particular resource
(say, a file descriptor # or what have you); (2) mapping the old resources
to new resources. (2) seems a bit slow and prone to all sorts of problems.
Perhaps a total system redesign would help, but that doesn't seem practical.
However, (2) may be ok if it would also employ (1), connected the mapped
resource to the unmapped resource when it comes available; things would
slowly speed up as resource assignments shuffle.
Other features would be to save a process and all children; to integrate
this with the core dump code; and of course, you should have a way to restore
this stuff.
I do not know how easy any of this is. It is just submitted as a thought,
in case it actually is far easier than I assume.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu