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 later).
Then you'll need to regenerate your rpm database.
Ric
John Wolford wrote:
>
> 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 --test
> and the -vv (double-verbose) option before doing it for real.
>
> That's just a brainstorming idea. Another would be to reinstall rpm from source
> (not source rpms, but source files).
>
> I'm interested to see how this turns out.
> j
>
> --- s <[EMAIL PROTECTED]> wrote:
> > 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. rpmdrake
> > (software manager) and kpackage seem to still work. I'm using 8.0.
> >
> > So, any advise how to repair the damage done, keeping in mind can't install
> > using rpm?
> >
> > TIA,
> > -s
> >
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Auctions - buy the things you want at great prices
> http://auctions.yahoo.com/
--
__________________________________________________________
Ric Tibbetts
Boeing Shared Services Group
UNIX System Administration
Seattle Server Operations
__________________________________________________________
