Neil Bothwick wrote: > On Mon, 8 Jun 2009 22:44:18 +0200, Alan McKinnon wrote: > > >> Is there an easy way to detect the orphaned libs on and old machine >> who's install dates back to 2004? The only idea I can come up with is >> >> for I in /usr/lib/*.so.* ; do equery belongs $I ; done >> > > qfile --orphans /usr/lib/*.so.* > > or, maybe cleaner > > qfile --orphans $(find -H /usr/lib /lib -type f) > > which avoids checking all the symlinks. > > Then run symlinks remove any dangling links left over. > > >
Questions: You knew I subscribed to this list. lol I ran the command: find -H /usr/lib /lib -type f | xargs qfile -o and I got a lot of hits. I'm just going to post snippets of the directories here. It is a LONG list otherwise. /usr/lib/gimp/2.0/plug-ins/ /usr/lib/perl5/site_perl/5.8.8/i486-linux/sys/ /usr/lib/python2.5/site-packages/dbus/ /usr/lib/python2.5/site-packages/Numeric/ /usr/lib/python2.5/site-packages/PyQt4/uic/ /usr/lib/python2.5/site-packages/Pyrex/Plex/ /usr/lib/portage/pym/ Some of those directories have additional directories in them but I tried to hit the highlights. Now to my questions. Can these be deleted? Should one make certain these doesn't belong to some package somewhere? Should I update my backups BEFORE deleting these? o_O If you want the whole list, let me know. Be forewarned tho, it is a huge list even if I leave out the kernel sources for my old trusty 2.6.23. Thanks much. Dale :-) :-)
