public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Pavel Machek <pavel@suse.cz>
Cc: John M Flinchbaugh <john@hjsoft.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Swsusp, resume and kernel versions
Date: Thu, 17 Feb 2005 15:09:51 -0500	[thread overview]
Message-ID: <d120d50005021712092241f9ec@mail.gmail.com> (raw)
In-Reply-To: <20050217195651.GB5963@openzaurus.ucw.cz>

On Thu, 17 Feb 2005 20:56:52 +0100, Pavel Machek <pavel@suse.cz> wrote:
> Hi!
> 
> > > 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.
> >
> > It could be a workaround. Still it will cause loss of unsaved work if
> > I happen to load wrong kernel. Given that the code checking for swsusp
> > image can be marked __init I don't understand the reasons gainst doing
> > it.
> 
> How do you know which partitions to check? swsusp gets it from resume= parameter,
> but if you do not have it compiled, you probably have wrong cmdline, too.
>

Ok, that makes sense. I guess I should just stop pulling vendor
kernels with the rest of updates since I am not using them anyway.

Sorry for the noise.

-- 
Dmitry

  reply	other threads:[~2005-02-17 20:10 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
2005-02-17 17:30     ` Dmitry Torokhov
2005-02-17 19:56       ` Pavel Machek
2005-02-17 20:09         ` Dmitry Torokhov [this message]
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=d120d50005021712092241f9ec@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=dtor_core@ameritech.net \
    --cc=john@hjsoft.com \
    --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