On Mon, 22 Jan 2007 12:41:37 +1100
David Woodhouse <dwmw2(a)infradead.org> wrote:
On Sun, 2007-01-21 at 17:29 -0700, Kevin Fenzi wrote:
> Yeah, one of the attempts I did a 'setenforce 0' before the yum
> It happened 3 times in a row, so I would think it's repeatable, then
> someone else was using the machine for a test and upgraded glibc and
> it worked, so not sure whats going on. Could prelink have anything
> to do with it? All my attempts were right after the install...
It's vaguely possible, but I don't see why prelink would result in
files just being _absent_.
> I will try and re-install and gather info for the bug soon.
> (Either tonight or tomorrow).
Ok. I finally found the time to do a bunch of re-installs and tracked
down the problem.
This box is a old surplus g4, and the cmos (PRAM?) battery is dead as a
doornail. So, powering up it has the time as being:
Thu Dec 31 17:45:43 MST 1903
If I do a update of glibc without setting the correct time, it blows up
in the manner I have seen. ie, /etc/ld-2.5.so gets blown away and the
machine is dead in the water. ;)
So, it's a bug, but a weird one. Do you still want me to file a bug?