> > 2) create the file yourself (it's still honored after all), which is time > consuming > > and error prone. > > (2) is the option you want, it's somewhat documented in the > README.Debian file and you can find examples in > /usr/share/doc/cpufrequtils/examples
With all due respect, I don't think it's documented very well: "This package provides the ability to set a chosen governor (different from the one configured at kernel compile time) at boot time boot time by setting the governor name in /etc/default/cpufrequtils. By editing that file [...] " Can't edit it if it isn't there. "Additionally loadcpufreq is a boot-time script that tries to detect and load the most appropriate cpu driver. You can override its behaviour by creating a /etc/default/loadcpufreq file. See the examples/ directory for sample configurations." >From README.Debian I'd assume that /etc/default/cpufrequtils is present by default while /etc/default/loadcpufreq is not. The bit about the examples at the end reads as if it was for loadcpufreq only. > Sorry, this will not happen. Maintaining user overridable config files > is a pain and using the ondemand governor by default is acceptable most > of the times. Nevertheless a file in /etc/default seems to be the standard way to set options regarding if and how to start /etc/init.d scripts. It's the first place I look for such options. From the number of config files I have in there the pain can't be all that bad :) Of course you're the boss ... but I'd prefer the bug to be reopened and tagged WONTFIX as I still think it's a valid concern. Cheers, C. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
