From: Pavel Machek <pavel@ucw.cz>
To: Rob Landley <rob@landley.net>
Cc: shoxx@web.de, linux-kernel@vger.kernel.org, mochel@osdl.org
Subject: Re: problem with suspend to disk on linux2.6-t9
Date: Tue, 18 Nov 2003 22:00:44 +0100 [thread overview]
Message-ID: <20031118210044.GA4172@elf.ucw.cz> (raw)
In-Reply-To: <200311180718.00059.rob@landley.net>
Hi!
> One thing that might be nice is if there was a way to trigger a resume from
> the initramfs. "Blow away the current process list and load this binary
> image of what userspace should look like." That way figuring out where the
> sucker lives is a problem you could punt on. :)
This is doable, but rather hard. Way too hard for 2.6.X, anyway.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
prev parent reply other threads:[~2003-11-18 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 22:27 problem with suspend to disk on linux2.6-t9 dodger
2003-11-17 23:43 ` Måns Rullgård
2003-11-18 8:45 ` Rob Landley
2003-11-18 13:18 ` Rob Landley
2003-11-18 18:38 ` dodger
2003-11-18 21:00 ` Pavel Machek [this message]
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=20031118210044.GA4172@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=rob@landley.net \
--cc=shoxx@web.de \
/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