5.3: redundant libraries in /usr/lib after cvsup-ing and build
des at des.no
Sun Oct 3 23:44:45 PDT 2004
spam maps <spamrefuse at yahoo.com> writes:
> A typical example is, when I do
> # ll /usr/lib/*libssh*
> 289008 Oct 3 17:28 /usr/lib/libssh.a
> 11 Oct 3 17:28 /usr/lib/libssh.so -> libssh.so.2
> 194148 Oct 3 17:28 /usr/lib/libssh.so.2
> 280822 Feb 24 2004 /usr/lib/libssh_p.a
> "Oct 3" is when I did my last build world.
> Is /usr/lib/libssh_p.a (Feb. 24) indeed redundant?
> Can I remove it, without breaking the system?
*_p.a are profiling libraries, which you probably disabled by adding
NOPROFILE=YES to /etc/make.conf. You can safely remove them.
> /usr/lib/libisc.so -> libisc.so.1
Old libisc from BIND 8. BIND 9 doesn't use it, but some ports may
want it. You should keep it around until those ports are fixed.
> /usr/lib/libkse.so -> libkse.so.1
This library has been renamed. You can remove it.
You can remove these.
Do *not* remove this, or you will be very sorry you did. It is normal
for ld-elf.so.1 to have a timestamp older than your latest build,
because installworld only installs a new ld-elf.so.1 if it differs
from the old one.
Dag-Erling Smørgrav - des at des.no
More information about the freebsd-current