Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
I have built and installed many packages from source, but am afraid I am almost completely ignorant as to how to best upgrade them...I have done many searches and really don't find much (which makes me think...). I will gratefully accept links to how-to's or other docs. RPM makes this easy, but there are certain packages I must build... on a similar note, what is the procedure to uninstall a package built from source?
I use this neat little program called InstallWatch to keep track of everything a package installs. Here's a link to the latest tarball http://asic-linux.com.mx/~izto/check...h-0.6.3.tar.gz. It is also used by a program called CheckInstall (IIRC) that will allow you to create rpm, deb, and tgz's of what you build.
I run a CLFS box most of the time (no package manager) and use InstallWatch all by itself to create log files in /var/log/CBLFS. I then have a couple of homegrown scripts. One cleans up the InstallWatch generated file and the other uses this information to remove all the files if I want. This approach doesn't take care of dependencies. I use an OOo spreadsheet for that!
Upgrading depends on the scope of the upgrade, IMO. "Big" upgrades like GNOME-2.14 to GNOME-2.16 requires a different strategy than upgrading appres-1.0.0 to appres-1.0.1. I install GNOME-2.14 in /opt/gnome-2.14 and make /opt/gnome a symlink to that directory. GNOME-2.16 then goes into /opt/gnome-2.16 and the symlink is changed. With my high-tech spreadsheet-based dependency tracker, I can figure out what apps depend on GNOME components and then rebuild them against the new GNOME stuff. Usually, I just wait until it pukes and then think, "Oh, yeah, I've got a new version of GNOME."