On Thu, Jul 03, 2003 at 06:37:19AM -0500, Ed Wilts spoke thusly: >On Fri, Jul 04, 2003 at 09:47:19PM +0800, Julian Gomez wrote: >> On Thu, Jul 03, 2003 at 01:05:04AM -0400, Edwin Robertson spoke thusly: >> >You didn't do -Fvh with the kernel did you? If so, that would cause any >> >version of Red Hat to toast itself. > >This is irrelevant. Fvh on a kernel is ok these days (I think).
OK, thanks for the update -- as I've stated myself, I think it can work also, but I'll be taking less risk next time. I'm a coward :-) (snip) >I'm willing to guess that you had previously installed an i686 version of >glibc and you just installed a 386 version on top. This is bad and >there have been many postings on this list related to issues that crop up >when this is done. There's a bugzilla entry as well, with >instructions on how to remove the bullet from your foot. Hmm. Possibly. I've just tried the following sequence of updates on RH v9, and everything seems to have come up fine on a test box. -> Plain RH v9, server config installed. -> All RPMs downloaded. -> glibc-* & kernel-* RPMs were moved to a different directory. -> All the RPMs minus glibc & kernel related ones were updated via 'rpm -Fvh *.rpm'. Rebooted the system. -> Downloaded the ftp://updates.redhat.com/9/en/os/i686/* rpm packages. -> Copied over 'glibc-2.3.2-27.9.i686.rpm' to the directory with the rest of the glibc related packages built for the i386 architecture. Ran 'rpm -Fvh *.rpm' on the glibc packages. Rebooted the system. I could not update with just the glibc-*.i686 RPM, was complaining about a dependency failing in regards to glibc-common. -> Installed all the kernel RPMs via 'rpm -ivh *.rpm' in the relevant directory. Rebooted the system. Everything works OK, at least I haven't seen a kernel panic just yet. >up2date is your friend. You should not try to download the errata >yourself unless there's a good reason you can't use up2date. I know, but $$$$ is a problem. >> Would you happen to know why the behaviour is different between RHv8 and >> v9 ? I'll follow your advice and try a brand new RH v9 install minus the >> kernel packages in the relevant directory. See whether the problem can >> be duplicated, or was it a daft user error of mine. > >If you're trying a brand new RHL 9 install, check the architecture of >the glibc package it installed - in fact, you should check all the >packages. Make sure that the architectures match when you pull down >your updates. Will do from now on. Thanks alot for everybody's feedback. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
