From: Pavel Machek <pavel@ucw.cz>
To: John Bradford <john@grabjohn.com>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: Separate ACPI_SLEEP and SOFTWARE_SUSPEND options
Date: Mon, 21 Jul 2003 01:00:13 +0200 [thread overview]
Message-ID: <20030720230013.GA1728@elf.ucw.cz> (raw)
In-Reply-To: <200307202020.h6KKKrxh003150@81-2-122-30.bradfords.org.uk>
Hi!
> > > > Right now you may boot without resuming and then later resume but
> > > > in meantime you cannot use those swap partitions/files which were
> > > > involved in suspending. Also in this case there is a risk that buffers
> > > > on disk won't match with saved ones.
> > >
> > > What happens on a machine which is sharing swap space between two
> > > operating systems? Do we have a way to mark a swap partition which is
> > > used for suspend data as unusable? Maybe we could change the
> > > partition type from 82 to something else.
> >
> > swsusp changes swap's signature, so swapon will fail.
>
> Aren't there some OSes that just blindly use the whole partition,
> without looking for a swap signature? I suppose that's really a
> problem that needs to be fixed with the other OS, though, to recognise
> the swsusp signature and disable swapping during that boot.
Exactly. If the other OS does not honour swap signature, it might as
well ignore partition type too. You need to fix that hypothetical
other OS.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-07-20 22:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-20 20:20 Separate ACPI_SLEEP and SOFTWARE_SUSPEND options John Bradford
2003-07-20 23:00 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-20 13:34 John Bradford
2003-07-20 18:40 ` Pavel Machek
2003-07-21 0:19 ` Horst von Brand
2003-07-20 13:04 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=20030720230013.GA1728@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).