On Sun, 2008-10-26 at 11:12 +0100, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
nordi wrote:
Carlos E. R. wrote:
While I agree that hibernating and powering off a computer that is doing nothing I tend to disagree. Even an idle computer does _something_: It waits for commands from its master, maintaining quasi-immediate availability (quasi, because the screen goes black, but thats ~1 second).
You removed the second part of my paragraph that changed the meaning :-)
However, if you want to be polemic, a computer that is waiting for input is said to be idling in computer parlance. Doing almost nothing. Some designs slow down the CPU, or even actually send the CPU to sleep, on those phases. Events such a keypress or a timing interval can awake it. No such feature on PCs.
Since the automatic sleeping seems to be on by default, this raises some questions: What mechanisms are in place to prevent the computer from going to sleep during an overnight compile job or download? What mechanism prevents a dual use desktop+server from going to sleep during lunch break? What about organizer-applications that want to (acoustically) notify me about something that's on my schedule while I am not using the PC?
Well, the logic could detect "how busy" is the machine.
Considering that, people may be, well, 'unhappy' about their computer going to sleep while it is supposed to be working. And this feature would probably be the first thing that I switch off.
Well, Magnus already has said that he would change the default.
Oh, I hope I didn't say that :-) I will try to get it changed as, in my opinion, it shouldn't suspend by default. Here's the bug report: https://bugzilla.novell.com/show_bug.cgi?id=439018 Cheers, Magnus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org