Tuesday, September 12, 2006

Symbolic Link Does The Fix

Few months ago, when Pat introduced a new module-init-tools package, i had a bad feeling about this package as it change how Slackware works in the way of looking of the file which contains what modules to be loaded at startup. In the old version, it looked at /etc/modprobe.conf, but with this new file, it will try to look at /etc/modprobe.d/ directory, so all file has to be put there. Look at the changelog that used to change this package
a/module-init-tools-3.2.2-i486-1.tgz: Upgraded to module-init-tools-3.2.2.
This new version of module-init-tools has been patched to look for module configuration information in /etc/modprobe.conf only for 2.4.x kernels. For 2.6.x kernels, files found in the directory /etc/modprobe.d/ are used instead. Eventually, /etc/modprobe.conf will be phased out in favor of the /etc/modprobe.d/ approach. If you have anything in your /etc/modprobe.conf that you need, and you are using a 2.6.x kernel, be sure to copy the configuration to a file (or files) in /etc/modprobe.d/.
Hint: ALSA expects sound modules to be configured in /etc/modprobe.d/sound.

I once tried to upgrade this package and all i got was totally stuck when the system tried to load the modules. At that time, i didn't know the solution was, so i used Piter Punk's module-init-tools package that just worked (it still uses the old ways). After some times, Piter Punk never upgrades his package and saying to use Pat's package, but i was afraid that i would get the same sympthoms again, so i keep using Piter Punk's package until today.

Last night, i upgrade my module-init-tools package along with libmtp and libnjb which has just been upgraded recently to give better support for udev and hotplug. I dare myself to upgrade to this version because i saw in the changelog that said Pat will make a symlink (symbolic link) to preserve backward compatibility for the old way. And i was thinking, so all i need is just making a symlink to the old modprobe.conf?? If this is the case, i would have done it few months ago, but that's ok. I'm still new to Slackware at that time, so it's common to do something that will break your own system. Luckily it worked well on my system. Finally i had a change to upgrade my outdated module-init-tools package. Thanks to symlink. You did a great job :)