3 ms·

Hibernate is not a requirement for everyone. First time I set up Arch Linux, I just never got round to setting up swap, and never felt any need for it either. O

Hibernate is not a requirement for everyone. First time I set up Arch Linux, I just never got round to setting up swap, and never felt any need for it either. Over the course of three years, I ran into OOM trouble four times (8GB of RAM was a lot in those days…). On my current laptop, I have a swap file and hibernation works fine (because this time I wanted to be able to switch over to Windows occasionally briefly without losing my session). It’s definitely more fiddly to set up in the Arch DIY style, but it’s still just following a set of instructions, so a distro that didn’t have the DIY philosophy could set it up easily enough.

chickenimprint 5y ago
Do you use multiple drives on your laptop? Because a single EFI system partition might become corrupted if you boot a system while the other is hibernated. Please refer to https://wiki.archlinux.org/title/Dual_boot_with_Windows#Fast_Startup_and_hibernation https://wiki.archlinux.org/title/Dual_boot_with_Windows#Fast...
- Macha 5y ago
  I think this is a little overblown. The old kernel ntfs driver which nobody uses and which is read only anyway ignores the fact that a drive is mounted by windows, so you could read corrupted data from the ntfs drive mounted by windows if windows hasn't fully completed writes that are hibernated, but you can't fuck up the partition because Linux won't write anything. The user space ntfs-3g, which is the one everyone actually uses, will refuse to mount a hibernated windows drive. The same appears to be true for the new kernel ntfs3 driver, since it's mount options include an option to force mount a dirty drive. If you use the options to force mount a dirty drive read/write, then yes, all bets are off, but you have to have dug pretty deep into your config to find out how to do that and at that point you have to know what you're doing.
  - chickenimprint 5y ago
    Sorry for the late reply. Okay, so I'm aware of the conundrums surrounding mounting the ntfs volume of a hibernated windows installation detailed on the wiki page. However, the same section clearly states that booting another OS even while a Linux system is hibernating can result in a broken EFI System Partition. This clearly does not relate to NTFS. I'm not knowlegdeable enough to understand the means by which this occurs, but I felt like I needed to give the person a heads-up before they brick their install.

chickenimprint 5y ago

Do you use multiple drives on your laptop? Because a single EFI system partition might become corrupted if you boot a system while the other is hibernated. Please refer to https://wiki.archlinux.org/title/Dual_boot_with_Windows#Fast_Startup_and_hibernation https://wiki.archlinux.org/title/Dual_boot_with_Windows#Fast...

Macha 5y ago
I think this is a little overblown. The old kernel ntfs driver which nobody uses and which is read only anyway ignores the fact that a drive is mounted by windows, so you could read corrupted data from the ntfs drive mounted by windows if windows hasn't fully completed writes that are hibernated, but you can't fuck up the partition because Linux won't write anything. The user space ntfs-3g, which is the one everyone actually uses, will refuse to mount a hibernated windows drive. The same appears to be true for the new kernel ntfs3 driver, since it's mount options include an option to force mount a dirty drive. If you use the options to force mount a dirty drive read/write, then yes, all bets are off, but you have to have dug pretty deep into your config to find out how to do that and at that point you have to know what you're doing.
- chickenimprint 5y ago
  Sorry for the late reply. Okay, so I'm aware of the conundrums surrounding mounting the ntfs volume of a hibernated windows installation detailed on the wiki page. However, the same section clearly states that booting another OS even while a Linux system is hibernating can result in a broken EFI System Partition. This clearly does not relate to NTFS. I'm not knowlegdeable enough to understand the means by which this occurs, but I felt like I needed to give the person a heads-up before they brick their install.