Some experiences on installing software on LINUX

For more information about how to install software on LINUX-general Linux technology-Linux technology and application, see the following. Whether or not the software can be successfully installed in LINUX will greatly affect your persistence in LINUX. when you first came into contact with LINUX, it was simply a crazy thing to install the software, it cannot be installed. Some friends who have been playing LINUX For A While know that with the increase of software installation, the later installation of software will become more and more smooth, because the foundation for installing software is gradually consolidated.

When a new system is installed, the most problems occur. This is because the foundation for installing software is poor.

To put it bluntly, there are some library files, some compilation and dependency environments, because the number of software installations increases, after the software is installed, the dependent files and dependent environments are all set up in the front. Therefore, the software is installed smoothly... I can't express my ability. I don't know how to describe this paragraph. If I can't talk about it, I will ask my friends who want to read the Post.

The following are some of the methods I have mastered and hope to help some friends...

1. Items that cannot be forgotten when installing the system! I recommend that you install "development tools" and "development libraries" in 100 projects when installing the system. If these two projects are not installed, basically, it can be declared that you cannot install software, especially the stuff in "development tools". You can click here to see what is in it and you will know why it is so important.

2. Install rpm or source code? If you are new to LINUX, I personally suggest using source code to install the rpm package. If the source code cannot be installed, do not affect the morale of a software, playing LINUX requires long-term persistence...

3. Install source code. The most common (not necessarily) and simple mode is

./Configure & make install & make clean

Generally, files with the words "README" and "INSTALL" are available in source code. We recommend that you read these files before installation, it usually tells you the required environment and file, installation method, default parameters and other information. Remember in ". /configure "read these files before, because some software has helped you with *. sh file (script file), you must run this script before ". /configure ". For example, the installation method of software in the perl environment may be" perl xx. xxx. xxxx ", for example," python xx. xxx. xxxx, etc.

After reading the instruction file, confirm that the First Command is ". /configure ", do not worry about this command, it is recommended to use ". /configure -- help "Check the installation parameters first. Otherwise, you will not know where the software runs after the confusing" make install, the default parameters of some software are listed in the "README" and "INSTALL" files ". /configure -- help. Therefore, I usually look at this stuff before compilation. It is inevitable that a problem occurs during software compilation. Remember to check the last few lines after compilation, and generally tell the success or failure, if the problem fails, you will be prompted where the problem is, and then solve the problem along the clues... this time will test your foundation and patience...

4. Install the rpm package. The common command format for installing rpm is
Rpm-ivh xx. xxx. xxxx

However, the dependency problem of rpm package installation is very serious. It is simply strange to have a high version or a lack of files. Sometimes when you install an rpm package, the system prompts that the dependency file is displayed on a full screen. In this case, use yum to remove the dependency file and then install the rpm package. Some friends may say that they can use -- nodeps for forced installation, but I do not recommend this (-- nodeps can be used frequently when the rpm package is uninstalled) because of dependency problems, even if you force the installation, it still cannot run in many cases. I don't think I should care about that space, and many dependent files will be used when other software is installed and running. The principle of installing the rpm package myself is: what is missing, the installation will be installed sooner or later...

5. yum install. I feel that when I install the rpm package, I often drag yum out to solve the dependency problem. The relationship is too close. When yum install xx. xxx. xxxx is run, some friends prompt:

No package xx. xxx. xxxx available. Nothing to do.

This means that this package does not exist in the source. You can use the yum list command to check whether there is any installation package for xxxx.

Yum list * xxxx *

In this way, you will not blindly fight.

6. Add a third source. In this case, it is likely that the third source can be added. Third-party sources can be yum software that is not available in official sources yum. Currently, most third-party sources are commonly used, such as linav, freshrpms, and fedora, in this case, yum install kmod-nvidia mplayer and so on cannot be found in official yum.

7. Add a DVD/CD image source (I don't know which term should be used to create an image source, haha ), because most of the dependent files can be yum from DVDs/CD, and the speed is fast, it can solve your urgent needs in the absence of network critical moments, so remember to spare, as to whether to disable at ordinary times, it depends on your own ideas. (It seems that most of the files downloaded now are dvd iso files)

I have installed a lot of software in LINUX. After some basic error solutions are accumulated, I will be able to get familiar with it. The above is my personal experience. If there is any error, please correct me and welcome to discuss it.