Scott Silva wrote:
on 8-20-2008 2:47 PM Kenneth Porter spake the following:
All of these prelink errors suggest that your binaries were
overwritten from a tarball installation. The easy fix is to erase
("rpm -e") the package and re-install it, likely upgrading to a newer
package at the same time.
But a rpm install will not overwrite the tarball install since tarball
installs usually go to /usr/local or under /opt while rpm installs will
go into /usr directly.
sure, but
- if you intend to always build from sources, you don't really care
about packages. it's only once you get a problem that you start becoming
more careful.
- however you do it, init scripts generally go under /etc (at least
under Linux).
I don't know if the tarball has a make uninstall
This almost never exists. it is not easy to implement (because you don't
want to remove files installed otherwise) without implementing a package
manager. an install.log would be nice though...
command, but the previous admin "should" have left the unpacked source
around from the install somewhere in either /root or in his home
directory. That can give more clues.
well, he could "should", but "he" generally would never :-)
OP can try to find the distribution that was installed from source and
use it to determine which files it installs, or he could ignore it and
only remove the files that create problems with a new version. if he is
motivated enough, reinstalling the whole system may be worth the pain.
........ d /usr/share/doc/dovecot-1.0/REDHAT-FAQ.txt
"d" files are documentation, and if you're tight on disk space, you
can suppress installation of documentation when the package is installed.
or buy more disk ;-p
