I disagree with this sentence. The machine is unhiberated in the same way that an unsuspend happens.
EVERYTHING is as it was before, except for one thing: Devices which are not known to be part of the machine, will have become detached, and if/when they reattach, configuration of them will be missing. But that is not what you are describing here, in fact it is wrong, because a softraid partition on a usb device (or similar) will be gone. So you are adding a detail which is unneccesary, but also inaccurate. If you add this sentence, the next one sentence someone will propose will likely be "network configuration" remains the same. Then, a sentence that your programs are still running. And on and on, trying to explain that this isn't like a reboot. But all of that "state-maintained" information is already implied, because that is what suspend/resume and hibernate/unhibernate means. Solène Rapenne <[email protected]> wrote: > hi > > I'm using an dedicated encrypted partition for a mountpoint and I was > wondering what would happen if I use ZZZ and then resume. > > - will it work out of the box? > - will it fail because the softraid device won't exist? > - am I going to be asked the passphrase by my rc.local script? > > It turned it worked out of the box, which mean the partitions remains > unlocked. In my opinion it's worth documenting, however I'm really not > sure how to word this in apm(8), here is an attempt > > diff --git a/usr.sbin/apm/apm.8 b/usr.sbin/apm/apm.8 > index ed110e11f14..61d414da8f1 100644 > --- a/usr.sbin/apm/apm.8 > +++ b/usr.sbin/apm/apm.8 > @@ -105,6 +105,8 @@ boot will occur, followed by the reading of the saved > memory image. > The image will then be unpacked and the system resumed > at the point immediately after the hibernation request. > +This implies that extra encrypted partitions (like an > +external disk) will remain unlocked after the resume. > .It Fl z > Put the system into suspend (deep sleep) state. > .El >
