you may not want to re-install from a source tarball I have don this once
and I totally jacked the rpm data base ( this is a very very bad thing)
however I will admit I should have nave typed make install.
and rescue mode would probably be the be the safest method of repair I
would recommend a
Been there on this one. The only way I found to fix it was to (first), install
RPM from a tar ball (available on the rpm website). Then once I had a working
rpm again, I overlaid it with the rpm version of it. (I deliberately installed
the tarball version in /usr/local to make it easy to extract
Hi all,
I was trying to make my gatway a little more secure when I moved the rpm
executable from /bin/ onto a floppy with plans on moving it back and forth as
needed. But this did not work. I moved it back and now get segmenation
faults when I try to install something from the command line.
This might seem extreme, but you could try to boot with a rescue disc (like the
install CD), mount your relevant partition, chroot and then try
updating/replacing the rpm package. I'd wait to hear what anyone else on this
list thinks before trying this. Definately you should run rpm with the
