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.
files ending in .tar.gz are generally source archive (kinda like zip) file. Most programs do not get installed simply by untarring and unzipping such files. You have to typically compile and install them. If you have not done compiling and installing then you can just remove the folder created after unzipping. It would be more worthwhile if you mention what distro you are using. If you are using rpm or debian based distro you already have a package manager which will make installing/removing packages a breeze.
If you've done the whole './configure' 'make' 'make install' dance, running './configure' (if your old one isn't there), 'make' and finally 'make uninstall' it will remove all traces of the old program. If you had custom ./configure variables, you need to make sure to put those in when you're compiling for the uninstall.
As at least one respondent pointed out, tar and gz are just compression and archiving formats. You can find a minimum of three things in a .tar archive:
A bunch of rpm files
A bunch of files + an install script
A bunch of files that allows you to compile the desired SW
How to undo the installation obviously depends on what you actually did....
If `make uninstall` doesn't work, try looking for a file called Makefile. Look for the 'install' target and then delete all of the files that it adds.
i do agree with you that "make uninstall" doesn't always work if the program has been installed from source after compiling it and doing all the steps like "./configure", "make", "make install" etc.
But i do not get the idea of the Makefile.
i searched for Makefile.......but there are large number of makfiles in the system.
So is there any master Makefile or should we concerned with the Makefile of the relevent program only ???
Do all installed programs have the Makefile ???
Sorry - I meant the Makefile for the application. For example, when I built and installed Apache 2.0.55, I extracted the sources to /usr/local/src/httpd-2.0.55. I have a file called Makefile in /usr/local/src/httpd-2.0.55 with several make targets. Here is part of that file showing the target for installing the man pages:
The fun part is looking through files and finding out what the variables translate to on the file system. Apache is pretty simple in that if you specify --with-layout=Apache in ./configure it ends up in /usr/local/apache2. Expect to spend a fair bit of time with some apps
I think all compiled apps will have a Makefile or a makefile, but they don't always have an uninstall target or even an install target (for example imap-2004e). The trick is to document what you do so that when you go back to work on it you don't have to guess or rely on memory.
checkinstall seems to be a better option for some particular distros.
README file for checkinstall::
# checkinstall 1.5.3 # #
# ######################## #
# Installs a compiled program from the program's source directory using #
# "make install" or any other command supplied on checkinstall's command #
# line. checkinstall will create a Slackware, RPM or Debian compatible #
# package and install it using your distribution's standard package #
# administration utilities. #