Le jeudi 10 f�vrier 2005 � 18:08 +0100, Marco d'Itri a �crit : > On Feb 10, Olivier Berger <[EMAIL PROTECTED]> wrote: > > > The documentation for module-init-tools lacks sufficient information > > about the role of modprobe.conf. > It has no role. Just do not use it.
Sure. I understood that after reading the modprobe.conf manpage (paradox ?) > > > If modprobe.conf is present, modprobe will ignore any modprobe.d files. > This is documented in modprobe(8) and the init script will warn if the > file is present but does not include modprobe.d/. > Pardon me but I don't find that in the modprobe(8) manpage. All I can find is : modprobe looks in the module directory /lib/modules/`uname -r` for all the modules and other files, except for the optional /etc/modprobe.conf configuration file and /etc/modprobe.d directory (see modprobe.conf(5)). All files in the /etc/modprobe.d/arch/ directory are ignored. I don't think it is clear enough about the fact that modprobe.conf is deprecated. > I think this is all that is needed. > Would you be so kind as to check again if the docs are accurate enough ? Thanks in advance. Best regards, -- Olivier BERGER <[EMAIL PROTECTED]> Ing�nieur Recherche - Dept INF INT Evry (http://www.int-evry.fr/) OpenPGP-Id: 1024D/6B829EEC
