Timeline for Save entire process for continuation after reboot
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Nov 26, 2018 at 21:33 | history | suggested | Joseph Young | CC BY-SA 4.0 | Update the dead link as mentioned in the comments |
| Nov 26, 2018 at 20:19 | review | Suggested edits | |||
| S Nov 26, 2018 at 21:33 | |||||
| Jun 6, 2017 at 9:18 | comment | added | starbeamrainbowlabs | @JohnP It's available on GitHub now: github.com/maaziz/cryopid | |
| Jan 25, 2017 at 21:20 | comment | added | John P | Has anyone tried this recently? The site is gone, I can't find a .deb, building from source fails, etc. I'd like to know if it's possible before spending any longer on it. I'm on Debian if it matters. | |
| May 7, 2016 at 15:33 | comment | added | cat | I didn't know FreeBSD and Linux were binary-compatible; that's something very interesting I just learned. But does that mean they have exactly identical memory models? It seems incredulous to me that they have the same syscall conventions, the same libc (i guess fbsd use glibc), the same exact calling conventions at the asm level, etc. The incompatibilities sound to me as if you took a MacOS process and dumped it onto a Windows box; that's really quite amazing. | |
| Jul 24, 2012 at 18:30 | comment | added | Tim | Used this before to save the state of a python script running on a Linux box and moved it to a FreeBSD box and resumed there. Some arcane magic going on there ;) | |
| Jul 24, 2012 at 18:29 | history | answered | Tim | CC BY-SA 3.0 |