site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Jan 1, 2008, at 2:55 PM, David Elliott wrote: On Jan 1, 2008, at 3:30 PM, Michael Smith wrote: = Mike _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... What exactly is the reason for requiring the system to go to sleep and then be woken up again? Closing the clamshell is an explicit instruction from the user to sleep the system. Your scenario is indistinguishable at the software level from my daily routine, where I close the lid on my MBP, pull all the cables from it and stuff it into my backpack. I don't stop to wait for it to sleep, or manually sleep it; I expect that when I close the lid, it will go to sleep and stay asleep. On Jan 1, 2008, at 3:02 PM, David Alger wrote: On Jan 1, 2008, at 4:55 PM, David Elliott wrote: Certain Apple portables do support running with the clamshell closed, but with other constraints applied that make it clear that the user intends for the system to be awake and that more or less require that it have adequate access to cooling (keyboard attached, external monitor attached, explicit wakeup after the clamshell is closed). If it doesn't have the cooling, it will get too hot. If and when that happens, the OS should halt the machine to prevent damage. Mac OS X is certainly smart enough to do this if temps reach an unsafe temp. You can't trust the OS to do it, and in fact the system doesn't; the SMC will shut the system down hard if it is headed for a thermal emergency. The point here being that an x86 Macintosh portable without airflow is almost certain to do this; a mode of operation that encourages the user to put the system into an enclosed space (bag, pile of stuff, etc.) is just not a viable thing. This email sent to site_archiver@lists.apple.com