From: John M Flinchbaugh <john@hjsoft.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Swsusp, resume and kernel versions
Date: Thu, 17 Feb 2005 11:28:47 -0500 [thread overview]
Message-ID: <20050217162847.GA32488@butterfly.hjsoft.com> (raw)
In-Reply-To: <20050217110731.GE1353@elf.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 705 bytes --]
On Thu, Feb 17, 2005 at 12:07:31PM +0100, Pavel Machek wrote:
> When all the vendor's kernels have swsusp, it will magically kill the
> signature. Or stick mkswap /dev/XXX in your init scripts.
This is what I've done in some instances. There should be no harm in
sticking that mkswap into your init scripts right before the swapon -a,
and then you have a nice userspace solution.
It's safe to reinitialize swap on any clean boot. A resume will not get
into the init scripts.
Just remember you're doing the mkswap if you decide to rearrange your
partitions at all, or code a script smart enough to grep your swap
partitions out of your fstab.
--
John M Flinchbaugh
john@hjsoft.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-02-17 16:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 4:46 Swsusp, resume and kernel versions Dmitry Torokhov
2005-02-17 5:15 ` Nigel Cunningham
2005-02-17 5:38 ` Dmitry Torokhov
2005-02-17 8:09 ` Nigel Cunningham
2005-02-17 21:05 ` Stefan Seyfried
2005-02-18 10:34 ` Nigel Cunningham
2005-02-18 11:23 ` Stefan Seyfried
2005-02-17 11:07 ` Pavel Machek
2005-02-17 16:28 ` John M Flinchbaugh [this message]
2005-02-17 17:30 ` Dmitry Torokhov
2005-02-17 19:56 ` Pavel Machek
2005-02-17 20:09 ` Dmitry Torokhov
2005-02-18 2:02 ` Bernard Blackham
2005-02-18 11:24 ` Pavel Machek
2005-02-18 12:26 ` Bernard Blackham
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=20050217162847.GA32488@butterfly.hjsoft.com \
--to=john@hjsoft.com \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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