SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Suspend to disk is indeed hibernate. It uses your swap partition (or a swap file, but I don't quite know how to set that up) to write the contents of the RAM and turns off your PC. When you start it up, as long as you have a line like append="resume=/dev/hda1" in your /etc/lilo.conf (assuming that your swap partition is /dev/hda1), your system will boot into the same state it was in when you hibernated. It should be noted that the default Slackware kernels do not have suspend to disk enabled by default, and also that these ACPI functions have greatly improved since the 2.6.21.5 kernel, so it would be best to use a recent kernel.
Suspend to RAM means that everything in your PC powers down except for your RAM (or something like this -- I am sure *some* other stuff gets powered as well, but it's very little). Suspending to RAM leaves my PC completely silent, and I've left it suspended for several hours with no ill effects. This functionality has also improved immensely since the 2.6.21.5 kernel (my PC crashed once or twice during suspend to RAM using that kernel but has never crashed using a 2.6.24.x kernel).
Standby basically means only a few things power down -- it's like "standby" in Windows. It's not really very useful considering how much better suspend to RAM is, in my opinion, but it's still an option.
I'm gonna go with suspend to RAM, although I can't at the moment as X crashes 9 times out of 10 when I shutdown / restart. This is a problem with X and the intel driver (Dell D430), which I hope will be fixed in 12.1.
I just couldn't get the hardware in my laptop to work with the standby or hibernate in slackware 11 with a 2.6.17.13 kernel.
Instead, I optimised the boot-up so that from completely off to command prompt it was about as fast as win xp coming out of standby on that laptop (and much faster than hibernate). Getting to the KDE desktop took longer, but battering away at keys and using pico is perfect for my daily commute on the train (emails, drafts to be tarted up later in OOo). Another advantage of this is that there is no steady drain on the battery.
I'll give hibernate/standby another go when 12.1 is ready.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.