On 09/16/2011 05:05 AM, Nils Philippsen wrote: > On Thu, 2011-09-15 at 14:32 -0400, Genes MailLists wrote: >> -------------- >> (i) Server. >> -------------- >> >> These run all the time - reboots are most often in maintenance >> window (or evenings / weekends for home servers) primarily if not soely >> for kernel updates. >> >> *** boot time pain more occasional fsck costs and not service startup >> >> Pain caused by O/S updates - rolling release model would be ideal >> for these. > > When I was dabbling with HA clustering (which was admittedly a long time > ago), there were environments with cold standby nodes (cold as in > "off"). If the hot node went down, the cluster management software > switched these standby nodes on, which booted normally then. In that > case, a small boot time would have been very appreciated. I'm not sure > if such scenarios are used nowadays. > > Nils Tho for that use case, would not a sleep/awake, as Adam suggested, have been far superior to a cold boot in that case? It could even work to quiesce a system and restore to running state for those processes doing real work without requiring the apps to manage their own restarts ... I assume it was power consumption being lowered here. Fast boot is of course desirable - I don't think anyone is against it obviously, I am merely suggesting it importance is somewhat limited in scope .. I also forgot marketing .. as in .. "Fedora boots faster than WingleBuntuDos/X running on same hardware in the MoronIX speed test :-) -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
