So, I've got this nice little PII-350 running smooth with RH9 EXCEPT for my up2date. For some strange reason I cannot register and update automatically. YES I upgraded certificates etc etc... Up2date does show me the latest versions of packages to be installed which I did manual.. AGAIN because my machine was trashed up twice when installing Glibc-rpm (i386).

Butt now I'm all up2date and want to update Glibc.
When I do e nice rpm -q --qf '%{arch}\n' glibc I get i686 ass an answer.

And now what? When I do the query on rpm for -common and -devel I get back i386. And Glibc is i686...

Now https://bugzilla.redhat.com/bugzilla...g.cgi?id=88456 shows me at the bottom of the page I can turn an i686 Glibc to an i386 Glibc.

http://www.linuxquestions.org/questi...pgrade+problem tells me it's better to upgrade with the i686 rpm (on a Xeon though).

I'm flipping coins now of which one to choose. An rpm -Uvh glibc-* with the i386 rpm's (cause I had to do it by hand) hosed my box twice so far...

One generic answer for n00bs like me would help many people I think.

Thanks In Advance!
Cheers!

Well, since nobody can tell me I did flip a coin and installed Glibc i686 for my PII-350. Pfew... Worked fine and still is stable.

The time I did this with the i386 rpm my system gave problems like in the links above causing the rpm-db to crash, Exit Line 121, respawning etc... with a dead machine as a result.

My advice updating glibc is to query glibc and install the package which is already installed. So do not "upgrade/update" an i686 to an i386... but stick with your system.

At least, that's my opinion after installing RH9 and configuring my server 4 times....

Greg