After several attempts to recover the situation using suggested methonds (I am not afraid of hard work) it became clear that the first suggestion - reinstall - was the smarter, easier, and ultimately the best way to resolve it. Done. Thank you - it was very educational. Regards.
"Thomas Lotterer" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > On Mon, Jul 19, 2004, v8625 wrote: > > Dear v8625, > > > I updated kernel on RedHat 9.0 [...] > > > as discussed on this list using /usr as a prefix was at least a brave > action. You must assume important parts of you OS were overwritten by > OpenPKG. I don't know whether it is worth the time repairing the system, > it is likely a reinstall is the faster route to go. But if you like hard > work, here are some hints: the FAQ lists where OpenPKG links itself into > the OS, see http://www.openpkg.org/faq.html#entry-points. Usually do a > "rm -rf $PREFIX" does huge parts of the job, but take care with your > particular prefix because it contains lots of non-OpenPKG files from > your OS! Assuming you have saved the OpenPKG binary RPMs you used to > ruin your system do a "openpkg rpm -qplv *.rpm" to query the files in > them. These are the files you want to get rid off. If they are surplus > files, remove them. If they replaced OS files, reinstall the OS package. > How do you know which OS package? "/bin/rpm -qf filename" will tell > you. Needless to say: both the openpkg and the OS rpm queries cannot be > performed on this defective machine and require another working "helper > machine". You can query a OpenPKG RPM with any "openpkg rpm" command, > the application doing the query and the RPM to be sniffed do not need to > share a common prefix, arch or os, i.e. a Solaris "/openpkg/bin/openpkg > rpm -qplv" can query a FreeBSD binary RPM build for /cw. That means that > the "helper machine" can be an arbitrary Unix device and you can use our > prebuild binaries to get a fast start. Regarding the OS rpm queries all > I can offer you is the output of our reference RHL9 machine. Also to > recover all libraries used by the system's /bin/rpm, here's what I found > out on our machine using > > $ /bin/rpm -qf `ldd /bin/rpm | awk '// { print $3 }'` | sort -u > bzip2-libs-1.0.2-8 > elfutils-libelf-0.76-3 > glibc-2.3.2-27.9.7 > popt-1.8-0.69 > rpm-4.2-0.69 > > Again hard work to be done: because /bin/rpm is not working you have to > watch out and copy the associated files from a good setup ... > > Good luck! > > -- > [EMAIL PROTECTED], Cable & Wireless > ______________________________________________________________________ > The OpenPKG Project www.openpkg.org > User Communication List [EMAIL PROTECTED] ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
