From: Bernard Blackham <bernard@blackham.com.au>
To: 7eggert@gmx.de
Cc: Ed Tomlinson <tomlins@cam.org>,
lokum spand <lokumsspand@hotmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: A possible idea for Linux: Save running programs to disk
Date: Mon, 3 Oct 2005 01:51:16 +0800 [thread overview]
Message-ID: <20051002175116.GE5211@blackham.com.au> (raw)
In-Reply-To: <E1EM7KO-00014G-CK@be1.lrz>
On Sun, Oct 02, 2005 at 07:08:43PM +0200, Bodo Eggert wrote:
> Bernard Blackham <bernard@blackham.com.au> wrote:
> >> Is there any kernel api that adding would make cryopid more
> >> dependable/cleaner?
> >
> > Currently a fair bit of information is obtained by injecting code
> > into the process's memory space, executing it, and reaping out the
> > results (eg, termcaps, file offsets, fcntl states, locks, signal
> > actions, etc). Can't think of ways to make it cleaner off the top
> > of my head, but I'm open to ideas.
>
> What about using an uml wrapper + vncserver?
Requires consciously doing so when you start it. It most certainly
could be done that way, but one of cryopid's aims is to work on any
running process without prior planning.
Interesting idea though - it'd be somewhat akin to porting
suspend-to-disk to UML (which has been on suspend2's todo list for a
while though :)
Bernard.
next prev parent reply other threads:[~2005-10-02 17:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4SXfo-7hM-9@gated-at.bofh.it>
2005-10-02 3:19 ` A possible idea for Linux: Save running programs to disk Bodo Eggert
[not found] ` <4T47e-5E-1@gated-at.bofh.it>
[not found] ` <4TbLq-2VG-5@gated-at.bofh.it>
[not found] ` <4TcR9-4sS-9@gated-at.bofh.it>
2005-10-02 17:08 ` Bodo Eggert
2005-10-02 17:51 ` Bernard Blackham [this message]
2005-10-02 19:13 ` Jeff Dike
2005-10-03 20:02 ` Pavel Machek
2005-10-01 21:30 lokum spand
2005-10-01 21:39 ` Arjan van de Ven
2005-10-01 22:21 ` Michael Concannon
2005-10-01 22:51 ` lokum spand
2005-10-01 23:09 ` Michael Concannon
2005-10-02 8:30 ` Tomasz Torcz
2005-10-02 13:31 ` Benoit Boissinot
2005-10-02 18:49 ` Jon Masters
2005-10-02 19:21 ` Lexington Luthor
2005-10-02 0:34 ` grundig
2005-10-02 4:53 ` Bernard Blackham
2005-10-02 12:57 ` Ed Tomlinson
2005-10-02 14:16 ` Bernard Blackham
2005-10-10 1:13 ` serue
2005-11-06 15:42 ` Bernard Blackham
2005-11-09 2:15 ` Peter Chubb
2005-10-02 5:36 ` Andrew Haninger
2005-10-03 17:41 ` Adrian Bunk
2005-10-03 18:52 ` Andrew Haninger
2005-10-03 18:59 ` Adrian Bunk
2005-10-03 19:48 ` Andrew Haninger
2005-10-02 18:46 ` Jon Masters
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051002175116.GE5211@blackham.com.au \
--to=bernard@blackham.com.au \
--cc=7eggert@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lokumsspand@hotmail.com \
--cc=tomlins@cam.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox