Fedora reawakens the hibernation debate [LWN.net]

Fedora reawakens the hibernation debate

Posted Oct 10, 2018 15:30 UTC (Wed) by cortana (subscriber, #24596)
In reply to: Fedora reawakens the hibernation debate by mcortese
Parent article: Fedora reawakens the hibernation debate

It's not done by GNOME/systemd but by the installation process. You mention you're on a Debian system. In your case, the installer would have set RESUME= in /etc/initramfs-tools/conf.d/resume to point to a swap device. This is copied into the initramfs when it is generated. At boot time, /usr/share/initramfs-tools/scripts/local-premount/resume makes that device available and then uses klibc's resume command to actaully perform the resume by writing the swap devices's major:minor:offset to /sys/power/resume.

to post comments

Fedora reawakens the hibernation debate

Posted Oct 13, 2018 18:05 UTC (Sat) by mcortese (guest, #52099) [Link] (2 responses)

Thank you for your explanation.

I still think it's fragile. This behavior of GNOME implicitly depends on initramfs. I think it should be made evident with a Depends-type relationship between the relative packages, otherwise a user could be tempted to use a kernel that doesn't need any initramfs and lose her unsaved data the first time she suspends her laptop for 3 hours after upgrading GNOME!

Fedora reawakens the hibernation debate

Posted Oct 16, 2018 8:32 UTC (Tue) by cortana (subscriber, #24596) [Link] (1 responses)

I'm sure the systemd folks would welcome patches to make logind's CanHibernate logic more robust!

Fedora reawakens the hibernation debate

Posted Oct 17, 2018 6:47 UTC (Wed) by mcortese (guest, #52099) [Link]

No automatic tool can detect if all the pieces are in place for a successful resume. The only sane choice would be to default to No unless the user explicitly opts in.