On Tue, Oct 24, 2006 at 01:43:13PM -0500, Henry Hollenberg wrote: > Yeah it was already pointed out to me that I must have compiled under > 2.6.17-amd64 instead of booting into 2.6.18-amd64 first and then running > the m-a stuff. Lots of steps, boy my butt is getting tired. > > Anyway, now I'm up against more missing executables in /usr/bin so I removed > the unstable lines from sources.list and ran: > > dpkg -l | grep ii | cut -d " " -f 3 | xargs -n 1 apt-get --reinstall install > > to brute force rebuild all the missing binaries/symlinks I deleted from > /usr/bin last week. > > So far I've added 20 new executables I had previously missed 1884 --> 1904 > on a 'ls /usr/bin | wc'.
How about: grep -l '/usr/bin' /var/lib/dpkg/info/*.list |sed -e 's/.list$//' That should list which packages should have files in /usr/bin, rather than every package installed (many of which do not have files in /usr/bin at all). -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
