On Fri, Feb 18, 2005 at 07:51:31PM +0100, Mattia Dongili wrote: > On Fri, Feb 18, 2005 at 01:46:17PM +0100, Francesco Paolo Lovergine wrote: > > Package: cpufreqd > > Version: 1.2.2-2 > > Severity: normal > > > > Just installed on my new thinkpad, all works but symlinks missed. > [...] > > -- debconf information: > > cpufreqd/no_pm: > > * cpufreqd/no_procfs_sysfs: > ^^^^^^^^^^^^^^^ > I suppose this is your problem actually: no cpufreq modules loaded (thus > no procfs nor sysfs interfaces available) so installation is aborted > there. Maybe you didn't see the debconf dialog because of a too low > priority? > > My problem (and bug) instead is to give some useful advice from the > init.d scrips if cpufreqd can't start :) and probably create the > symlinks in any case so the user is better warned. > > If you agree and my suspects are I'll change the bug title. > --
Indeed, I loaded the modules _after_ the installation. Probably creating the symlinks anyway and establishing availability of needed modules at run-time is better. Also, at least documenting the thing in README.Debian. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
