Package: sysfsutils Version: 2.1.0-6 Severity: important Hello,
the sysfsutils init-script should depend on the start of the
cpufrequtils init-script:
Currently, the init-script depends on the start of loadcpufreq - most
likely to be able to configure cpufreq governors, but this dependency
is not necessarily sufficient to really be able to configure them.
A cpufreq governor has not just to be modprobed but it also has to be
selected before its configuration is made available through sysfs. While
loadcpufreq modprobes them, cpufrequtils selects one.
On legacy boot this was not an issue, because sysfsutils started after
cpufrequtils (because it alphabetically orders behind), but with
dependency-based boot the situation changes: it is now started before,
while, or after cpufrequtils depending on what insserv and startpar
choose.
Patch attached.
Btw... I personally believe that sysfsutils should start somewhere close
to procps since both do a similar job. The latter currently starts in
rcS, which IMHO makes sense because it eases the dependencies of daemons
enormously. Would you mind moving sysfsutils to rcS if I'm getting the
cpufrequtils maintainer convinced to move to rcS, too?
regards
Mario
--
Das Gegenteil einer trivialen Wahrheit ist falsch;
das Gegenteil einer grossen Wahrheit ist ebenfalls wahr.
-- Niels Bohr
diff -urN sysfsutils-2.1.0.orig/debian/sysfsutils.init sysfsutils-2.1.0/debian/sysfsutils.init --- sysfsutils-2.1.0.orig/debian/sysfsutils.init 2010-07-24 08:28:02.000000000 +0200 +++ sysfsutils-2.1.0/debian/sysfsutils.init 2010-07-24 08:28:40.198216293 +0200 @@ -3,7 +3,7 @@ ### BEGIN INIT INFO # Provides: sysfsconf # Required-Start: mountkernfs -# Should-Start: udev module-init-tools loadcpufreq +# Should-Start: udev module-init-tools cpufrequtils # Required-Stop: # Default-Start: 2 3 4 5 # Default-Stop:
signature.asc
Description: Digital signature
