Hi, Patrick Shanahan schrieb: > yes, I have reached that problem. What next, manually copy files from > midnight commander to the correct locations ??
Now you have basically two choices: 1. Use a program or script that can unpack RPMs without using rpm. 2. Use the rescue system. Try 1. first. The script is here: http://www.iagora.com/~espel/rpm2cpio Download it, rename it to rpm2cpio.pl (to avoid confusion with the "real" rpm2cpio), copy it to /usr/local/bin and make it exectuable. Now download rpm.x86_64 http://download.uni-hd.de/ftp/pub/linux/suse/update/10.1/rpm/x86_64/rpm-4.4.2-43.4.x86_64.rpm and extract it somewhere (preferably an otherwise empty directory): rpm2cpio.pl rpm-4.4.2-43.4.x86_64.rpm | cpio -id Now copy the extracted files manually to their location. Important: rpm will probably work again, but copying the files manually will not register rpm itself in the rpm database. So you should rpm-install rpm on top of the manually extracted files: rpm -Uvh rpm-4.4.2-43.4.x86_64.rpm And a general hint: Use "rpm -U", not "rpm -i" when installing packages. This might help avoiding double installed packages (-U replaces an existing package which is the right thing in most situations, -i will install a new package in addition to the existing one). If that fails, try 2. Boot into the rescue system, mount your / file system and use rpm -Uvh --root=/mountpoint rpm-4.4.2-43.4.x86_64.rpm to reinstall rpm on the rpm-less system. Andreas Hanke --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
