Package: module-init-tools
Version: 3.12-1
Severity: normal

Multiple issues:

First issue: The manual page for modules(5) makes the claim that
"The /etc/modules file contains the names of kernel modules that
are to be loaded at boot time, one per line." while the
/etc/init.d/module-init-tools script actually attempts to execute
the lines in /etc/modules as commands launched from the shell.

Second issue: Consider the pathological case that you put a module
name in /etc/modules and then a system update adds a command to a
$PATH directory such as /bin or /sbin with the same name as the module.
At system boot time the /etc/init.d/module-init-tools script will
no longer load the module, instead it will just run a command
unrelated to loading the module.


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages module-init-tools depends on:
ii  libc6                         2.11.2-7   Embedded GNU C Library: Shared lib
ii  lsb-base                      3.2-23.1   Linux Standard Base 3.2 init scrip

module-init-tools recommends no packages.

module-init-tools suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to