Comment 6 for bug 8832

#include <hallo.h>
* Marco d'Itri [Sun, Sep 12 2004, 11:26:17AM]:
> On Sep 12, Eduard Bloch <email address hidden> wrote:
>
> > Really, I expected that a tool like update-modules
> > still reads /etc/modprobe.d and created /etc/modprobe.conf, and I spent
> root@wonderland:~#cat /sbin/update-modules
> #!/bin/sh -e
> if [ -x /sbin/update-modules.modutils ]; then
> exec /sbin/update-modules.modutils "$*"
> fi
> exit 0
> root@wonderland:~#

That is no the point. I expected the update-modules from
module-init-tools to create /etc/modprobe.conf (because of the apparent
"modules*" -> "modprobe*" name transition). Believe it or not,
upstream thinking != user thinking.

> update-modules has never created /etc/modprobe.conf, BTW.

I see, but something has created it. And messed up few things here.

> > - separate paragraph in the modprobe and modprobe.conf manpages!
> Please send a patch.

Attached.

> > - a warning appearing when the init script starts and modprobe.conf
> > exist and something in modprobe.d/ exists as well. Eg.
> This would be bogus, modprobe.conf may include modprobe.d/.

Possible, but also dealt with by the patch below.

Regards,
Eduard.
--
"The quiet ones are the ones who change the universe.
 The loud ones only take the credit."
                                                               L.M. ItB