Slack glibc upgrade gone bad

[ph34r]

I was upgrading glibc to 2.2.5 from the -current directory. I tested this on a "don't matter" machine at work, and all went well. I burned the packages to CD, took it home and fubar'd my box. Seems I had a bad burn (xcdroast didn't report any errors) because the md5sums are now different from the packages I downloaded vs. whats on the cd.

Anyway, glibc is now screwed on my system. I have a plan to recover, but I want some other input first. The plan is to boot with the boot/root disks for Slack 8, then run pkgtool, and then install packages from a different directory. The only packages I plan on installing will be the glibc 2.2.5 updates. Then reboot, and hope for the best.

Will this work? Is there a better way? TIA for help.

[Killer_Penguin]

That seems about the best way to me.