On 21-01-2012 20:13, Karol Blazewicz wrote:
On Sat, Jan 21, 2012 at 9:08 PM, Mauro Santos <registo.mailling@gmail.com> wrote:
Today when updating, module-init-tools was replaced by kmod, everything went smoothly and my machine boots fine, however I have a doubt, where should module configuration files be placed, /etc/modprobe.d or /lib/modprobe.d?
Will both directories be supported in the long run or is this a temporary thing not to break most systems?
Mauro
http://mailman.archlinux.org/pipermail/arch-dev-public/2012-January/022330.h... Tom Gundersen wrote: In general, and regardless of kmod, packages should install their config files in /lib/modprobe.d, and leave /etc/modprobe.d to admins.
This works (in module-init-tools, as well as in kmod) in the same way as with udev's rule files. If a file foo.conf exists in both /etc and in /lib, the version in /etc is used and the one in /lib is ignored. This means the admin can easily override the standard config files supplied by the packages, and the package updating the config file does not create .pacnew/.pacsave files.
Exactly what I wanted to know, thanks :) -- Mauro Santos