* New upstream release. (Closes: #254204)
* Now /etc/modprobe.d/ is processed by modprobe. This means that
/etc/modprobe.conf and /lib/modules/modprobe.conf are not needed
anymore and update-modules is now a no-op. Executable scripts in
/etc/modprobe.d/ are not supported anymore.
/etc/modprobe.conf will be removed or moved to /etc/modprobe.d/.
Previously, /etc/modprobe.conf was automatically generated, so I suppose that on
upgrade, the file could contain duplicate configuration data.
Surely this could be handled better, though.
The reason seems to be this:
module-init-tools (3.1-pre2-1) unstable; urgency=medium
* New upstream release. (Closes: #254204) modprobe. conf and /lib/modules/ modprobe. conf are not needed modprobe. d/ are not supported anymore. modprobe. conf will be removed or moved to /etc/modprobe.d/.
* Now /etc/modprobe.d/ is processed by modprobe. This means that
/etc/
anymore and update-modules is now a no-op. Executable scripts in
/etc/
/etc/
Previously, /etc/modprobe.conf was automatically generated, so I suppose that on
upgrade, the file could contain duplicate configuration data.
Surely this could be handled better, though.