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
update.
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, thanks.
--
dwmw2