Linux Common Software Installation method __linux

Current LINUX packages can usually be found from the release CD or from the Internet. Its general format source code and executable code two kinds. To save disk space or download time, most of the software is packaged to exist in a compressed file format.
Common packages are like file.tar.gz, file.src.tar.gz, file.rpm, and so on.

Before introducing the common installation method, it is necessary to remind you to first develop a good habit of operation. Because of the advanced nature of LINUX design and the features of multi-user use, you can follow the following guidelines as much as possible throughout the installation process:

1. If you don't want to mess up your catalog, you'll need to build a readable directory before downloading the software. And not only you can understand what it means. At the same time, it's easy to remember what's in it next time you see it.

2. Unless the software is installed solely for the purpose of installing the software, it is necessary to have a backup directory before installing the software, preferably offsite backup.   Designed to store your favorite or important software packages. 3. Before you try out a new software, do not try it on a machine that is currently running business or has important data but has not yet been properly backed up. That is not to take risks.

4, in the installation as far as possible as ROOT execution of various orders. After the installation is complete, check the permissions carefully.

5, the installation of the temporary directory generated as far as possible put it into the/tmp directory. The beginning of a good practice is to put the software to be installed in the/TMP directory at the outset. Don't forget to delete it after you are sure that it has been installed successfully.

6, know your CPU and LINUX version type, download the appropriate software package. If a variety of formats exist, it is recommended to use the RPM format package. Because it is easy to use and easy to make mistakes.

7, for the. RPM end of the package, simply execute RPM-IVH file.rpm on the line. If it hints that something is missing, then it has to be fully mended first. If it prompts that the package has been installed, but may be incomplete or otherwise you want to force the installation of the package, type the following command: RPM-IVH--replacepkgs file.rpm.

8, in the installation of RPM software package may encounter a variety of conflicts. In particular, when you want to install the latest package in the older version, there are often some similar tips:
Failed dependencies:
Kernel >=2.2.10 is needed by file. x.x.x
File. x.x.x=0.80.1 is needed by otherfile.y.y.y
This kind of information indicates that you need to upgrade your Linux kernel to 2.2.10 in order to use the new software, and you must install another package otherfile.y.y.y to install file.x.x.x. The--nodeps option allows you to ignore the review of package dependency issues, but this practice is often not recommended.

For software packaged in the RPM format, if previous versions of the software were previously available, it is generally preferable to use the upgraded mode rather than the installation mode, as the configuration file can be retained. Even if the old version does not exist, the upgrade mode will not go wrong.
Therefore, the following commands can be used: RPM-UVH file.rpm.
For more information on RPM, see the other articles in this site:

Because Linux advocates DIY and advocating individuality, in order to make the software more suitable for your machine, but also in order to advocate open source and the spirit of sharing, will generally be in the form of source download. If you get a package like this, you'll have to recompile the package after you unzip it.

First put the package in the/tmp directory, and then execute
Tar zxvf file.src.tar.gz.

At this point, you usually have to see which directories are unpacked, whether there is a readme or install software. If so, please read it carefully first. If you can understand it, then you don't have to look at this document. The general steps are: Make;makeinstall such two steps. Obviously, the use of gcc--this should be available in all distributions. It usually asks which directory to put in the software installation. Generally to the/usr directory put on the line. If the/usr directory is set as a read-only partition (this is usually based on security considerations), it can be placed in the/home/bin/local/bin/file directory. The premise is that this is also one of your good habits. The next time will not be able to find the line.

If you are using a well-known release such as Redhat, there will be an intuitive and Easy-to-use package-specific tool pkgtool. The name will vary depending on the distribution. At this point, the installation of the software package can be completed as long as it is clicked between clicks.