On Wednesday 01 November 2006 07:47, Stuart Henderson wrote: > On 2006/11/01 14:15, Anton Karpov wrote: > > After many years of upgrades (probably starting from 3.3 or 3.4, don't > > remember) my box has a lot of old libraries in /usr/lib. I'm pretty sure > > I have no hand-build third-party software depends on them, and with every > > upgrade cycle I update all packages along with release (thanks to espie@, > > it's so easy now). So I think it's completely useless in my system, only > > wasting disk space in /usr. And it's safe to remove those old libs. Am I > > right? It would be nice to mention it in the FAQ. > > There's a bunch of other things that might be hanging around too - > if they're taking up enough space that you want it back, a reinstall > may be a better idea. > > Since you're the one who gets to fix it if it breaks, you can > do what you like :-) But if it's in the FAQ, someone will follow it, > miss something important, have a problem and complain...
You aren't going to save a huge amount by removing the old cruft, but I do understand that it builds up over time. I live on -current on my laptop and have this problem too. The ldd program is your friend here, in that you can verify that you don't need libc.so.old.old anymore. If you are unsure of the removal of something, move it to a temp space (NOT /tmp, since you are likely to have rebooted before you figure out that you need something!), and see what happens. You are likely to mess up once or twice, so you'll learn what the current versions of things are. --STeve Andre'
