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 -F ( freshen) for safety. this should just replace damaged files. >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/ John W. Bloodworth Senior linux support technician This answer was provided by the Sutherland Support Center. We provide solutions for most of your Linux needs. (800) 431-3787
