rcache

[Log in to get rid of this advertisement]

Hello All, this is my first post to LQ and I'm fairly new to CentOS.

Attempting to install CentOS-5 kept ejecting CD saying something like, no CD was found with CentOS install files. So I figured maybe if I installed an older version and upgraded I'd avoid the hardware issue. Since I've never done an upgrade with this distro in this way I used the upgrade "not recommended" on the CentOS.org website.

http://wiki.centos.org/HowTos/Migrat...verCD_4.4_to_5

There were some version differneces between what was on the migration guid and the actual RPM index, but they were all minor so I figured that it was ok to use the later ones in the current index. found here:

http://mirror.centos.org/centos/5/os/i386/CentOS/

When I got to the section to "Remove deps/outdated packages", running the rpm command:

rpm -e VFlib2 caching-nameserver autofs kudzu pcmcia-cs xorg-x11 newt-perl hal crypto-utils --nodeps

gave me this:

rpm: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory

Now anything using rpm give errors including yum and to top it off I'm remote and to go reinstall is not impossible but fairly difficult as I am a couple hours away.

I'm currently attempting to reinstall rpm and just discovered that there is no compiler installed (searched for cc and gcc).

Any suggestions are greatly appreciated!!!

unSpawn

Maybe your installer CD wasn't OK. Did you verify the hash?


Install the right nss RPM by hand? Doubt that'll be the end of it though.


The "upgrade path" you choose is problematic to say the least because I'm pretty sure there have been major RPM/SQLite/Python changes between Centos-4 and Centos-5. Like said at EE I *really* would stress finding a way to cleanly install Centos-5: in the end this will prove to be the least error-prone, most efficient and most stable solution. That said, with 'rpm2cpio filename.rpm|cpio -idm' you should be able to get most things into place (run the 'rpm -q filename.rpm --scripts' parts manually) after which you can 'rpm -i --justdb filename.rpm' to update the RPMDB. I would also like to say that "give errors" isn't as qualitatively good as posting (or attaching files containing) exact error lines.