4 ms·
> whether detecting changes and initating a more complete boot or dealing with it in the GUI. Sure, they can detect hw changes and make full cold boot, therefo
by mkup 15y ago
> whether detecting changes and initating a more complete boot or dealing with it in the GUI.
Sure, they can detect hw changes and make full cold boot, therefore losing all RAM data which was saved to the disk at the point of hibernation. (It would be like a quick dirty reset.) Or they can restore that data back to RAM and crash the kernel instantly. In either case, RAM contents are lost.
So each time I turn off the PC, I have to plan ahead, "do I want to use poweroff-type-I or poweroff-type-II option?" If I won't guess right, then I lose my data.
- polshaw 15y agoThis new 'power off' isn't meant to be a full hibernate. It only stores the kernel-related RAM, not your data. So you would only lose your kernel data, which would be reloaded in the 'full' boot. Full hibernate is still a separate entity (or at least, a part of standby as i'd predict). This is not a change from now; if you hibernate and then change your hardware, yes, you will lose data.
- mkup 15y agoOK, now I get the idea Still there could be some edge cases - like hibernating filesystem cache as a part of kernel-related RAM , then shutting down, booting Linux, changing the filesystem and then booting windows (which does not know that filesystem pages were changed from outside and working with obsolete copy from cache). This one is a non-issue actually, because Linux ntfs-3g driver deletes hiberfil.sys when mounting NTFS partition in R/W mode, but there could be other edge cases like this one.
- mkup 15y ago... A firmware upgrade, for example. Or some jumpers changed.