|
Home > Archive > Linux/Unix > December 2003 > Another question
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| mindmesh 2003-12-09, 9:15 pm |
| I want to remove Mozilla from my system and then install Firebird. How do I go about removing Mozilla? Would I just delete the .mozilla file? And then what about the .netscape and .netscape6 files? Thanks. | |
| Boulware5 2003-12-09, 11:33 pm |
| You using RedHat? If Mozilla was installed in rpm format, to delete a program, use (as root):
# rpm -e programname | |
| Papiya 2003-12-10, 7:41 am |
| Never just delete a program on a UNIX system. All decent distros have package management systems. Any package will likely have hundreds (if not thousands) of separate files placed throughout the filessytem. So you should always use one and only one pakcage management system. Red Hat and most Linux distros use, RPM, but there are others . . . DEB packages for Debian-based systems, tarballs for Slackware (note: Not all tarballs are Slackware packages . . . Slack packages have a do_install.sh script that is executed after the tarball is unpacked). Find out what your system uses and then uninstall it that way.
The dot files in your home directory are configuration files for those programs. Deleting them will do nothing except erase your user-specific configurations for those apps. | |
| mindmesh 2003-12-10, 9:11 am |
| Mozilla was installed when I installed the RH 9. The system uses RPM's but I don't think rpm -e Mozilla will work. Don't I need the actual package name?
I read there is a way to view installed packages but I don't remember the text I pulled that from. Any ideas? Thanks for the responses. | |
| Papiya 2003-12-10, 9:15 am |
| To get an alphabetically sorted list of all packages on your system, use the following command sequence:
# rpm -qa | sort | less
The queries all of the packages. I think rpm -e mozilla should erase the package, but in case it requires you to type out the whole name you can query all packages to see what the exact name of it is. Globbing should work as well. I always keep a list of installed programs in my home directory, but using the above query and redirecting the output to a file. That way I can browse it easily and then I just update it when I change anything. | |
| mindmesh 2003-12-10, 9:36 am |
| Thank you. Works liked like a charm. Next question is:
I can only find Firebird as a tarball. So if I install it that way is there a way to unistall it? Or should I just redirect the output of the MakeFile to another file? Thanks again. | |
| Papiya 2003-12-10, 10:08 am |
| quote:
Originally posted by mindmesh
Thank you. Works liked like a charm. Next question is:
I can only find Firebird as a tarball. So if I install it that way is there a way to unistall it? Or should I just redirect the output of the MakeFile to another file? Thanks again.
There are two programs that you should be aware of:
1. Checkinstall: http://asic-linux.com.mx/~izto/checkinstall/
This utility allows you to install tarballs and still keep track of where all the files are so that when you uninstall or upgrade you won't have left over stragglers laying around.
2. alien -- You can usually get this at www.rpmfind.net if it doesn't comewith your distribution. It will usually translate between the major package formats . . . there is actually very little difference between the various formats, but they are important as they all use their own particular database to track the packages.
Last, but certainly not least, when you build a program from the source, you usually go through a series of steps like this:
./configure
make
make install
The first command searches your system for required components and configures the Makefile. The "make" step builds the program. The probem is with the "make install" step. What that does is usually take the different files and throws them to the four winds . . . the binaries get send to one directory, libraries to another, headers to another, manpages to another, etc. So . . . if you get a INSTALL file that tells you to run all of these steps, run the first two but STOP before you execute "make install". That way, everything stays in the directory that you built it in. My suggestion would then be to place the entire directory under the /opt directory and add the paths the the binaries to your PATH environment variable. This way, when you need to get rid of the package, you just delete the entire directory. Otherwise you would need to look at the Makefile to see where everything was sent to, and then write a script to delete them all.
This third method should be a last resort. try the first two before you do this.
Let me know if you need more info. |
|
|
|
|