From: Arjan van de Ven <arjanv@redhat.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Nigel Cunningham <ncunningham@clear.net.nz>,
Pascal Brisset <pascal.brisset-ml@wanadoo.fr>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
swsusp-devel <swsusp-devel@lists.sourceforge.net>
Subject: Re: [Swsusp-devel] Re: [PATCH] Allow initrd_load() before software_resume() (version 2)
Date: 06 Aug 2003 13:47:31 +0200 [thread overview]
Message-ID: <1060170451.5848.2.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20030806113045.GB583@elf.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 494 bytes --]
On Wed, 2003-08-06 at 13:30, Pavel Machek wrote:
> Hi!
>
> > Okay. I hadn't tried it yet. I'll happily take up the barrow for you and
> > push it to Pavel and Linus with the rest, if you like.
>
> Don't even think about that.
>
> It is not safe to run userspace *before* doing resume. You don't want
> to see problems this would bring in. Forget it.
>
so how do you resume from a partition on a device mapper volume?
(and yes I basically agree with your sentiment though)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-08-06 11:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 0:29 [PATCH] Allow initrd_load() before software_resume() Pascal Brisset
2003-08-01 1:18 ` Nigel Cunningham
2003-08-01 10:32 ` [PATCH] Allow initrd_load() before software_resume() (version 2) Pascal Brisset
2003-08-01 10:41 ` [Swsusp-devel] " Nigel Cunningham
2003-08-06 11:30 ` Pavel Machek
2003-08-06 11:47 ` Arjan van de Ven [this message]
2003-08-06 12:57 ` Pavel Machek
2003-08-06 13:16 ` Måns Rullgård
2003-08-11 2:08 ` Rob Landley
2003-08-11 15:29 ` 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=1060170451.5848.2.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@clear.net.nz \
--cc=pascal.brisset-ml@wanadoo.fr \
--cc=pavel@ucw.cz \
--cc=swsusp-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).