On Thu, 27 Oct 2005, Dennis Peterson wrote: > I consider all obsolete libraries to be debris and get rid of them. They > have no value and I don't need to waste tape space backing them up.
Unless you have binaries built against the older versions that will suddenly start to fail when you delete that supposed debris. > Moreover, folks who are sloppy about not cleaning up libraries tend also > to be sloppy about managing the executables, too, and how many posts have Completely different situation. Executables don't have version numbers, the new version overwrites the old. > But if you wish to trust your systems to survive accumulating libraries, > by all means do. I don't think its a line item on anyones best practices > page, though. It's on mine. I've NEVER had a problem because of the existance of an old library. If you do, you're doing something wrong. Only problems are when one was deleted that was still used. In fact my 'best practice' calls for libraries believed to be old to be tarred up for at least 6 months, makeing them unaccessable but easily restoreable when that not-often run program fails. ========================================================== Chris Candreva -- [EMAIL PROTECTED] -- (914) 967-7816 WestNet Internet Services of Westchester http://www.westnet.com/ _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
