> Puzzling... > > I did a manual glibc and kernel upgrade on an Athon 1333 (older T-bird > not XP) recently and it worked fine. I got two of the "INIT: id "x" > respawning ..." type messages but it continued just fine. Sorry I didn't > note the exact messages. > > That machine is solid and in daily service. I wonder what the difference is? > > Could it be as simple as the command syntax? In the bug report it's: > > rpm -Fvh glibc* > > But on my Athlon I used: > > rpm -Fvh i386/glibc-common-2.3.2-27.9.i386.rpm > i386/glibc-debug-2.3.2-27.9.i386.rpm > i386/glibc-devel-2.3.2-27.9.i386.rpm > i386/glibc-profile-2.3.2-27.9.i386.rpm > i386/glibc-utils-2.3.2-27.9.i386.rpm i386/nscd-2.3.2-27.9.i386.rpm > i686/glibc-2.3.2-27.9.i686.rpm i686/nptl-devel-2.3.2-27.9.i686.rpm > > (all on one line) > > I support some older systems too and have separate scripts for i386 and > i686 updates. For kernel "upgrades" I install the new version manually, > test, then edit grub.conf when it works. > > I how that helps, You should take a look at yum: http://linux.duke.edu/yum/ it's an updating program that handles multiple archs just fine and gets them correct. -sv
