From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Finding orphaned libs
Date: Mon, 08 Jun 2009 18:52:23 -0500 [thread overview]
Message-ID: <4A2DA437.2070501@gmail.com> (raw)
In-Reply-To: <20090608215408.3c4b4c91@krikkit.digimed.co.uk>
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
:-) :-)
next prev parent reply other threads:[~2009-06-08 23:53 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 20:44 [gentoo-user] Finding orphaned libs Alan McKinnon
2009-06-08 20:54 ` Neil Bothwick
2009-06-08 22:10 ` Alan McKinnon
2009-06-08 22:57 ` Dale
2009-06-08 23:31 ` Willie Wong
2009-06-09 10:05 ` Joerg Schilling
2009-06-09 10:54 ` Neil Bothwick
2009-06-08 23:52 ` Dale [this message]
2009-06-09 0:18 ` Willie Wong
2009-06-09 0:27 ` Dale
2009-06-09 7:03 ` Alan McKinnon
2009-06-09 13:01 ` Mike Kazantsev
2009-06-10 7:53 ` Dale
2009-06-10 8:37 ` Mike Kazantsev
2009-06-09 13:33 ` Volker Armin Hemmann
2009-06-09 13:48 ` Joerg Schilling
2009-06-09 14:04 ` Volker Armin Hemmann
2009-06-09 14:34 ` Neil Bothwick
2009-06-09 14:51 ` Joerg Schilling
2009-06-09 14:08 ` Mickaël Bucas
2009-06-09 14:15 ` Joerg Schilling
2009-06-09 14:36 ` Neil Bothwick
2009-06-09 14:42 ` Paul Hartman
2009-06-09 14:52 ` Neil Bothwick
2009-06-09 14:59 ` Joerg Schilling
2009-06-09 15:29 ` Neil Bothwick
2009-06-09 15:21 ` Etaoin Shrdlu
2009-06-09 15:28 ` Neil Bothwick
2009-06-09 15:20 ` Etaoin Shrdlu
2009-06-09 15:30 ` Alan McKinnon
2009-06-09 14:39 ` Mickaël Bucas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A2DA437.2070501@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox