From: Adam Feuer <adamf@pobox.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Pavel Machek <pavel@suse.cz>,
Swsusp mailing list <swsusp@lister.fornax.hu>,
ACPI mailing list <acpi@phobos.fachschaften.tu-muenchen.de>,
kernel list <linux-kernel@vger.kernel.org>,
Gabor Kuti <seasons@falcon.sch.bme.hu>
Subject: Re: [swsusp] Re: swsusp for 2.4.14
Date: Tue, 20 Nov 2001 18:07:15 -0800 [thread overview]
Message-ID: <20011120180715.N11355@sunflower.zipcon.net> (raw)
In-Reply-To: <20011121001858.B183@elf.ucw.cz> <E166M8H-0003QH-00@the-village.bc.nu>
In-Reply-To: <E166M8H-0003QH-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Wed, Nov 21, 2001 at 01:24:57AM +0000
Quoting Alan Cox <alan@lxorguk.ukuu.org.uk>:
> Has anyone tried porting swsusp to user mode linux. That way you could
> actually "suspend" a copy, resume it in parallel with the original and
> compare the two memory images ?
Alan,
I got swsusp-2.4.13 (from Florent) to compile on User Mode Linux
2.4.13, with a couple of changes... it seems to suspend, but will not
resume afterwards... just boots normally. Suspending doesn't seem to
write the swsusp signature to the swap partition...
I haven't gone any farther than that yet. I can provide a diff
against uml-2.4.13 if anyone is interested in helping. :-)
cheers
adam
--
Adam Feuer <adamf@pobox.com> http://www.pobox.com/~adamf/
next prev parent reply other threads:[~2001-11-21 2:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 23:18 swsusp for 2.4.14 Pavel Machek
2001-11-21 0:50 ` H. Peter Anvin
2001-11-21 1:24 ` Alan Cox
2001-11-21 2:07 ` Adam Feuer [this message]
2001-11-21 4:12 ` [swsusp] " Jeff Dike
2001-11-21 2:47 ` undocumented, ungoogleable /proc/net/nicinfo interface Blue Lang
2001-11-21 15:46 ` [swsusp] Re: swsusp for 2.4.14 Pavel Machek
2001-11-21 18:53 ` Jeff Dike
2001-11-23 13:46 ` Pavel Machek
2001-11-25 0:50 ` Jeff Dike
2001-11-21 15:45 ` Pavel Machek
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=20011120180715.N11355@sunflower.zipcon.net \
--to=adamf@pobox.com \
--cc=acpi@phobos.fachschaften.tu-muenchen.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=seasons@falcon.sch.bme.hu \
--cc=swsusp@lister.fornax.hu \
/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