On Monday, 25 September 2006 16:51, Luca Tettamanti wrote:
> On 9/25/06, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> > On Monday, 25 September 2006 10:40, Pavel Machek wrote:
> > > So let's do:
> > >
> > > before suspend, swap header says "this is swapspace"
> > > suspend image is written, header says "this is image, suspend time was
> > > 5 seconds"
> > > then comes powerdown, powerup, reading image, and its overwrite with
> > > "this is almost swapspace, suspend time was 5 seconds, resume time was
> > > 3 seconds"
> > > then comes atomic restore
> >
> > and now it's _expected_ to be swap space.
>
> I guess that before unfreezing the processes it's safe to have a
> broken swap space; but if it's frozen suspend cannot read and reset
> the swap header, right?
No, suspend is not frozen. Otherwise it wouldn't be able to unfreeze the
rest of processes.
> I suppose that there's no way to preserve the "new" initrd across the
> atomic restore? Otherwise the content of the ram disk is usually
> available under /initrd after boot.
After the resume that should be the image you have used to for the
first time boot (ie. before the first suspend).
Greetings,
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Suspend-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/suspend-devel
