Obviously what the distro people were doing was trying to make sure that these tasks were always done, even by Windows-oriented folks who "automatically reboot" when something peculiar happens.
The purpose of ldconfig
is to update the "shared library cache," which enables Linux to find shared libraries (think, "DLLs") quickly and accurately. ex minimis,
this command must be run whenever a shared library is changed, but that actually doesn't happen often and most Makefiles will do that step for you when they do.
The purpose of depmod
is to update the kernel-module dependency map.
This tells commands like modprobe
which kernel-modules (loadable parts of the kernel...) depend upon which others, so that if you ask to load a particular module, all of the modules that it needs will be loaded as well. Once again this is something that must
be done if you change a kernel module, but once again, how often do you actually do that? Answer: not very often.
need to be mindful ... very mindful
... of the fact that you are now changing something that the distro-writer put into place and subsequently may now rely upon
being done. I cannot say whether ordinary installation and/or updating of "packages" on your system may expect, and require,
that these operations which you have now omitted will be done upon the next reboot. One would hope that they covered their bases in these two areas by other means than these, but if for whatever reason they did not you may need to (and thus, will need to know how to)
run these commands yourself at appropriate times.