Package: module-init-tools
Version: 3.2-pre1-2
Severity: normal
Hi.
The documentation for module-init-tools lacks sufficient information
about the role of modprobe.conf.
If modprobe.conf is present, modprobe will ignore any modprobe.d files.
As many documents (HOWTO, etc.) will suggest additions to modprobe.conf,
there is a high risk that an administrator will create the file and thus
mask all previous configuration instead of adding something into
modprobe.d/
Btw, the documentation concerning modprobe.conf should be updated in
order to state that.
At the present time, modprobe's man page is not very clear since it
refers to modprobe.conf's man page. But this one won't discuss
modprobe.d.
You have to read update-module's manpage to know about it :
Note that the file /etc/modprobe.conf is not the exact equivalent
of /etc/modules.conf. It is not required for module-init-tools
and is not generated any more. In fact, most people
should not create that file since /etc/modprobe.d/* would
be ignored in this
case but Debian packages store their additional
configuration files in /etc/modprobe.d/.
I suggest that module-init-tool add a some documentation about that, and
maybe a README in /usr/share/doc/module-init-tools to explain that
modprobe.conf is somehow obsoleted... or a dedicated modprobe.d manpage
?
Thanks in advance.
Best regards,
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-200501201
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages module-init-tools depends on:
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
