Hi, I agree with Cesare, for various reasons. First, it seems completely unreasonable to use the init script to do something else than starting the daemon. Secondly, if we are to belive [1] (and to this day I have yet to find any compelling argument against these good practices), the only sane default when frequency scaling is availble is ondemand.
Having the setting set up at boot time as part of a system-wide configuration script makes more sense (akin to sysctl.cnf). This would save memory, a tiny bit of boot time (fast boot is one of the goal of Jaunty) and reduce the crowd of daemon idling on one's system. Ultimately, if someone, for any reasons need to have the behaviour : performances on AC / powersave on Batteries or any other kind of custom behaviour, then he should install powernowd or cpufreqd or whatever himself and tailor it to his need. This is certainly not the case of 90% of laptop users. [1] : http://www.codon.org.uk/~mjg59/power/good_practices.html -- cpu-scaling setup initscript should be moved to new package https://bugs.launchpad.net/bugs/93409 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
