On Friday, 25 July, 2003 02:29, David Demner wrote: > (snip) > I remember pretty much everything on my machine was hooped, including ls, rpm, > etc... > So you probably will need physical access to the box with a recover disk/cd.
Well I suppose I can consider myself lucky then, since almost everything seems to be still running fine, except mainly the rpm system :) > (snip) > Well, I guess you could check out > > http://www.redhat.com/swr/i686/glibc-2.3.2-27.9.i686_fl.html > > which at least lists all the files that rpm would install for you. Maybe you can > get a non-rpm version of glibc (like from http://ftp.gnu.org/gnu/glibc/), unpack > them into a directory (assuming tar/gzip/bzip still work) and read the INSTALL > doc... That may help. Aah that's a really helpful link. I'll try to do this then. Actually I had downloaded the source rpm for the old glibc(2.2.4), and read and applied the INSTALL file that came with it. The 'make' went fine, but I was a little scared to do a 'make install' with this stuff. I didn't want to destroy what still worked, especially since that source came with a lot of patches that I am not sure how and if they can be applied. But now I can maybe look at the differences beetween the contents of the 2 versions of the rpms and replace the files one by one with the ones I obtained from the SRPM I compiled manually, and see what works and what doesn't. Or maybe this will break everything by creating inconsistencies within the library files... and I should use make install. > (snip) > Probably related to the glibc problem, but probably not because of the messed up > upgrade. > There was a patch to qmail that changed the reference to errno, which was changed in > updated versions of glibc: > > http://article.gmane.org/gmane.mail.qmail.general/13960 > > and it's probably this. Apply the patch (I actually had to update qmail by changing > the qmail code manually since the patch didn't work), recompile, and hopefully the > error will go away. Ah yes I read something about it, and since this upgrade took my glibc from 2.2.4 to 2.3.2 I suppose it could have triggered this bug. I'll look into fixing this later, thank you for the link. Thanks a lot again, I'll try to carefully find a way to cure my poor system with this info ;-) Olivier -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
