RedHat 7.0, stock kernel, various updates. I just ran up2date to see what's available for updating on my RedHat box. I use up2date because it's an easy way to keep track of what's been updated and what hasn't. Typically, I'll pick and choose "safe" packages to update. Anything that looks to be complicated I reserve for separate download and update.
Among the pkgs listed was apache and I selected it for update. Upd2date then advises me of a bunch of other packages that would require updating, including mod_ssl and openssl. This is all well and good, I knew I needed to update openssl, anyway, so I let up2date update that stuff, too. It all appeared to download and install OK. Unfortunately, after trying to restart apache (service httpd restart), apache wouldn't start. There was an error with loading /etc/httpd/modules/libssl.so, "version GLIBC_2.2 not defined in file libc.so.6 with link time reference". I also received a similar error WRT up2date when I tried running it. I "solved" the error with apache by moving /etc/httpd/modules/libssl.so out of the way. But I still have the up2date error: "ImportError: symbol __sysconf, version GLIBC_2.2 not defined in file libc.so.6 with link time reference" So, I think I've resigned myself to needing to upgrade glibc from 2.1.92 to 2.2.4. As best as I can tell, libc.so.6 is symlinked to libc-2.1.92.so, which is provided by the glibc-2.1.92-14 RPM. Upgrading glibc, should resolve this. At least that's my current theory, anyway. I've read thru the SxS on glibc, and the recent NetLlama thread regarding glibc and feel relatively secure in attempting this update, but I have a few questions I'd like to throw out there before jumping in... Should I use the glibc rpms that RedHat provides for 7.0, or compile glibc, following the instructions at linux.nf? There are 4 RPMs at ftp://ftp.redhat.com/pub/redhat/linux/updates/7.0/en/os/i386/ that pertain to glibc. If I install using them, I'll at least know that everything will be put where RadHat wants, and the RPM database will remain intact. I assume that such an update should be done without users on the system, but should I be in runlevel 1 when doing the update? Should I update my kernel first, before updating glibc? If I do the kernel, should I go with 2.4.16, which I would have to compile, or the 2.2.19 kernel, which I can get from RedHat via RPM? It seems that RedHat expects users of 7.0 to be on a 2.2.x kernel, should that matter? As always, any help is appreciated. Regards, Tim _______________________________________________ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
