MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
"is there a system file and link checker that will clean the install?"
The first thing to do is to rebuild your rpm data base to make sure it is not corrupted:
I don't know of a command that will magically clean the install. apt-get might do it and then again apt-get might get part way through the job and blow up. You can use the rpm verify option to check the packages that you suspect are corrupt. You can get a list of every package on your system with:
rpm -qa | sort | less
Then you can check the ones that you may have messed up (using gimp as an example) with:
rpm -V gimp
When everything is OK rpm -V gives no messages. If you get a message then there is an error in that package's installation. You can straighten out the messed up packages by using the rpm --force option (using gimp as an example):
However if the problem is mismatched version numbers among the dependencies then using --force immediately is a bad idea. If you have mismatched version numbers then find all of the mismatches and write them down. Decide what versions of which packages you need and then install the correct version of each package over the incorrect version using --force.