1. Default Repository Manager: such as yum, apt-get, homebrew, you have to learn the main stream repository and deployment management system on you distribution.
2. Default Package Manager: such as rpm, dkpg, you need to learn the shell command about software installation shell command. And these command usually provide a database to record the relationship between package's dependencies. You might have a lot customized software package that provide by vendor which you can not found the open source software on public repository for you to yum or apt-get.
3. Useful shell command `locate`: we usually use this command to learn the installation made by ./configure and `make install`. This command is really useful when you have some cutting edge software that compiled and installed manually by your own. Usually, sometimes we use the command to check the library missing or any misconfigure package installation.
4. Finally, you have to check the following folder like /etc/init.d on CentOS for your command about `service` or `sbin/service` and `chkconfig`. These are the command for you to lookup the application would be started at booting.
5. If the file does exist but you still have trouble on link it, you could use ldd command to parse the ELF binary for checking all the dependencies' location such as
[user@server ~]$ ldd /usr/lib64/libtdsodbc.so.0
linux-vdso.so.1 => (0x00007fffe3ea0000)
libodbcinst.so.2 => not found
libgnutls.so.26 => /usr/lib64/libgnutls.so.26 (0x00007f65b1a6a000)
librt.so.1 => /lib64/librt.so.1 (0x00007f65b1862000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f65b1645000)
libc.so.6 => /lib64/libc.so.6 (0x00007f65b12b0000)
libtasn1.so.3 => /usr/lib64/libtasn1.so.3 (0x00007f65b10a0000)
libz.so.1 => /lib64/libz.so.1 (0x00007f65b0e8a000)
libgcrypt.so.11 => /lib64/libgcrypt.so.11 (0x00007f65b0c14000)
/lib64/ld-linux-x86-64.so.2 (0x00007f65b1f71000)
libgpg-error.so.0 => /lib64/libgpg-error.so.0 (0x00007f65b0a10000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f65b080c000)
