From: mru@users.sourceforge.net (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Re: Resuming from software suspend
Date: Fri, 19 Sep 2003 12:15:12 +0200 [thread overview]
Message-ID: <yw1xoexhkrtb.fsf@users.sourceforge.net> (raw)
In-Reply-To: 1063965939.7874.6.camel@laptop-linux
Nigel Cunningham <ncunningham@clear.net.nz> writes:
> If your filesystems were mounted readonly and the boot won't mount them
> writable, you should be fine with no special precautions. Last time I
> looked at 2.6 code, it didn't fix the suspend header when you use
> noresume. If that's still true, you should be able to boot with the
> noresume option, and then later normally.
What I want to do is boot, do some things, and then resume the
suspended state without rebooting between. Is that possible? I don't
see any reason why it should be impossible to do, even if it's not
currently supported.
--
Måns Rullgård
mru@users.sf.net
next prev parent reply other threads:[~2003-09-19 10:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 20:02 How does one get paid to work on the kernel? Nigel Cunningham
2003-09-19 7:51 ` Måns Rullgård
2003-09-19 7:59 ` Nigel Cunningham
2003-09-19 8:10 ` Måns Rullgård
2003-09-19 9:31 ` Nigel Cunningham
2003-09-19 9:45 ` Resuming from software suspend [was: Re: How does one get paid to work on the kernel?] Måns Rullgård
2003-09-19 10:05 ` Nigel Cunningham
2003-09-19 10:15 ` Måns Rullgård [this message]
2003-09-19 10:27 ` Resuming from software suspend Nigel Cunningham
2003-09-19 11:09 ` Måns Rullgård
2003-09-19 10:40 ` Pavel Machek
2003-09-19 13:34 ` Bas Mevissen
2003-09-19 13:40 ` How does one get paid to work on the kernel? Bas Mevissen
2003-09-19 13:51 ` Måns Rullgård
2003-09-19 13:58 ` Bas Mevissen
2003-09-19 14:09 ` Måns Rullgård
2003-09-19 17:51 ` Jan Rychter
2003-09-23 12:07 ` 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=yw1xoexhkrtb.fsf@users.sourceforge.net \
--to=mru@users.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.