On Sun, Feb 11, 2007 at 12:31:14PM -0600, Robert Hancock wrote: > Willy Tarreau wrote: > >Nigel, don't take it as a personal offense, but I think it is a very > >centric view of Linux usages. Where I work, Linux is used a lot on > >servers and appliances. It is used for mail relays, HTTP proxies, > >anti-viruses, firewalls, routers, load balancers, UTM, SSH relays, > >etc... Nobody would ever want to enable power management on those > >machines, let alone suspend which would cause a major havoc, would > >the system decide to enter suspend for any reason. > > > >Many people also have Linux on their notebooks, but as a dual-boot. You > >read the word ? "dual-boot". It means that they cleanly shutdown their > >system every time they don't use it anymore, and they won't know what > >OS they'll use next time. > > > >I've never heard anyone there complaining "oh, I'm fed up with this > >boring boot, I always have to wait 30 seconds when I need to do > >something, I wish I could suspend and resume". It is considered the > >normal way of using their PCs. > > I think your experience is rather different than that of Joe Average > User who doesn't frequent kernel lists, and also I think you'll find > that for a lot of Linux laptop users that don't use supend, the reason > is that it doesn't work reliably, quite often due to driver issues.
I would believe it if I knew people using suspend/resume on the other OS. But that's not the case either. Also, it happens that with today's RAM sizes, suspend-to-disk then resume can be several times slower than a clean fresh boot. When you have 1 GB to write at 20 MB/s, it takes 50 seconds to shut down, and as much to restart. Compare this to 5-10 seconds for a shutdown and 30-50 seconds for a cold boot, and it might give you another clue why there are people not interested in such a feature. Regards, Willy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/