public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@users.sourceforge.net>
To: Andreas Jellinghaus <aj@dungeon.inka.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Swsusp-devel] [PATCH 2.6]: suspend to disk only available if non-modular IDE
Date: Wed, 31 Mar 2004 08:23:16 +1000	[thread overview]
Message-ID: <1080685396.13014.3.camel@laptop-linux.wpcb.org.au> (raw)
In-Reply-To: <1080631869.1118.12.camel@simulacron>

Hi.

On Tue, 2004-03-30 at 17:31, Andreas Jellinghaus wrote:
> > That should be doable, provided that the initrd doesn't mount anything.
> > Decryption is 'interesting'. The key needs to be set up in the resumed
> > kernel too. (Shouldn't be a problem, if you manage to suspend to it!).
> 
> I don't know if loading modules can be done without, but the usual way
> is to mount /sys and /proc so you can see what hardware is available.

They would be fine. The key thing is that none of the filesystems which
have journals get mounted. That would cause the crash recovery routines
to run, resulting inconsistency between the image on disk and the one
that the suspend image contains. You could probably do just about
anything, so long as those filesystems aren't mounted. Assuming that is
done, actually calling suspend after an initrd is run shouldn't be a
problem, so far as I know.

Regards,

Nigel

-- 
Nigel Cunningham
C/- Westminster Presbyterian Church Belconnen
61 Templeton Street, Cook, ACT 2614.
+61 (2) 6251 7727(wk); +61 (2) 6253 0250 (home)

Evolution (n): A hypothetical process whereby infinitely improbable events occur 
with alarming frequency, order arises from chaos, and no one is given credit.


  reply	other threads:[~2004-03-30 22:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-28 19:36 [PATCH 2.6]: suspend to disk only available if non-modular IDE Arkadiusz Miskiewicz
2004-03-28 23:37 ` [Swsusp-devel] " Nigel Cunningham
2004-03-28 23:47   ` Nigel Cunningham
2004-03-29 21:34     ` Andreas Jellinghaus
2004-03-30  6:52       ` Nigel Cunningham
2004-03-30  7:31         ` Andreas Jellinghaus
2004-03-30 22:23           ` Nigel Cunningham [this message]
2004-03-30 20:11   ` Pavel Machek
2004-03-31 22:36     ` Nigel Cunningham
2004-04-01  7:26       ` 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=1080685396.13014.3.camel@laptop-linux.wpcb.org.au \
    --to=ncunningham@users.sourceforge.net \
    --cc=aj@dungeon.inka.de \
    --cc=linux-kernel@vger.kernel.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