Package: module-init-tools Version: 3.3-pre11-1 Severity: minor I am trying to blacklist a module from udev while allowing the admin as well as acpid to modprobe it. Since udev does not have a blacklist facility but relies on module-init-tools, I proceeded to blacklist the module in /etc/modprobe.d. The effect was that udev would no longer load the module, but neither would the acpi script called by acpid, which does nothing but modprobe $MODULE, work any longer. I can still modprobe from the command line.
If I look at the modprobe.conf manpage's blacklist section, nothing suggests any of the above behaviour. Could you please extend the manpage to explain what's going on? -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.20-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages module-init-tools depends on: ii libc6 2.5-9 GNU C Library: Shared libraries ii lsb-base 3.1-23.1 Linux Standard Base 3.1 init scrip module-init-tools recommends no packages. -- no debconf information -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems
signature.asc
Description: Digital signature (GPG/PGP)
