Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
My question is short and I guess simple for more advanced users.
Should I delete older version of library after upgrading it to the newer version? I have upgraded glibc and gtk+ and deleted older versions, after rebooting my box some of the applications didn't want to start ... so I am little confused now ... Can you help me?
for the most part, if I upgrade something like glib, gtk, atk, etc.. I like to place it back in /usr.
For glibc, ya gotta read the docs. the normal procedure for installing glibc is to overwrite the old one, not
install the new one and delete the old one ( the both use the same files, so when you removepkg, it's gonna pull some of your new files out you just installed)
between your two post here, it might be better to upgrade to 10.0 or 10.1 otherwise your gonna be compiling for awhile to bring slack 9.1 up to date.
just my $.02
Well, I'll tell you how I do it, but this is mostly personal preference. when I compile a new lib/application, I look in /var/log/packages to see if it is already installed on my system. If it is there, then I replace it, If its not, then I (generally but not always) install to /usr/local. It really doesn't matter in the long run all that much, just try to keep things together ( like gtk, glib, atk, pango. etc... all in the same prefix, kdelibs and apps in the same prefix, etc...). As for glibc and gcc, I don't replace them unless I am forced to. They are not that hard to do, but sometimes you can run into more problems than what the upgrade is worth.