Tag Info

New answers tagged

3

If you can select the OS to boot, then it means you are going past a bootloader, so resuming from disk, not from RAM. The scenario you describe isn't possible with suspend to RAM.


3

Suspend may be to RAM and/or to disk. If you suspend and can boot another OS, than for sure you have suspended to disk. If you close the lid of a laptop and then on reopen can work almost immediately then you probably had a suspend to RAM, but this doesn't allow you to boot another OS (as the OS suspended this way immediately reactivates). The suspend to ...


0

since you only use the secondary hdd for backup, I would suggest telling fstab not to mount the drive automatically and to make a backup script that mounts the drive, makes the backup and unmounts the drive again. example of the fstab line with the noauto option: /dev/sdb1 /media/backup ext4 user,noauto 0 0 bash script for the backup would than begin ...


0

This answer is building on the answer suggested from @gnp. The difference being that to reduce the risk of vlock locking of virtual console/terminal switching being impacted by the usual pm-suspend etc hacks that tinker with the consoles. Similar the answer of @gnp we need two files /etc/pm/sleep.d/20_lock_with_countdown (with +x file permission) ...


1

This sleep.d script should work (replace <youruser> with a user you've got the password for. I ran it with root the first time and couldn't get back in): #!/bin/sh case "$1" in hibernate|suspend) ;; thaw|resume) USER=<youruser> /usr/bin/vlock -ans & echo $! > /var/run/vlock.pid ...



Top 50 recent answers are included