On Thu, 23 Sep 2004, Oliver Neukum wrote: > Swsusp goes through a sync - suspend - resume - write image - suspend > cycle to bring down the machine. There's a certain logic to that because > after a reboot all devices will be running.
Can you give me a pointer to the swsusp code? Also, why the first suspend? Why not sync - resume - write image - suspend? After all, any devices that get suspended there will wake up immediately during the resume step. > This cannot make a difference. Consider that one of the lists may be > empty. I fail to see the logic. Please elaborate. You can have systems > where you can shut down nothing without shutting down the swap > device. I _said_ that I don't fully grasp all the implications and requirements here. But okay, let's suppose that we're doing the first suspend on your list. Clearly this isn't an actual power-off suspend; otherwise nothing would be alive to carry out the rest of the list. So the question of whether or not to shut down the swap device doesn't matter. Even if it was shut down, the resume step that comes next would wake it up. Now let's suppose we're doing the second suspend on your list, the actual power-off suspend. Since the memory image has already been written, there's nothing wrong with shutting down the swap device. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
