Linux system rookie management top ten common error inventory

No matter what kind of system you use, the management system can't be missed. But for systems like the Linux system that we don't often touch, management is a nightmare, but no matter what. Is there a rookie process, what mistakes do these rookies make?

Error one: download and install various types of applications from various channels without strict review

This may be a good idea. If you are running Ubuntu, you will know that the package manager is using it. Deb package. However, many of the applications you find are available in source code. No problem? These programs may work properly after installation. But why can't you install the program at will? The reason is very simple. If you install the program as a source, your package management system will not be able to track what you have installed. So, what happens when package A (installed as source) depends on package B (installed from a .deb library) and package B is updated from the update manager? Package A It may or may not work. However, if both packages A and B are from. If the deb library is installed, the chances of both running will be higher. In addition, updating packages is easier when all packages come from the same binary type.

Error 2: Ignore Updates

This is not to say that Linux administrators lack skills. However, many Linux administrators, after running Linux, thought that nothing would be done in the future, thinking it was safe and reliable. In fact, new updates can patch some new vulnerabilities. Maintaining updates can create a watershed between a vulnerable system and a secure system. Linux security comes from constant maintenance. In order to achieve security, in order to use some new features and stability, any administrator should keep up with the pace of Linux updates.

Error three: bad passwords

Remember that the root password is usually the key to the linux kingdom. So why should the root password be so easily cracked? It is important to ensure the robustness of your user password. If your password is long and difficult to remember, you can store this password in an encrypted location. When this password is needed, the decryption software can be used to unlock the password.

Error 4: Booting the server into X

When a machine is a dedicated server, you might think of installing X, so some administrative tasks will be simpler. However, this does not mean that the user needs to boot the server into X. This will waste valuable memory and CPU resources. Instead, you should stop the boot process at level 3 and enter command line mode. Not only does this leave all resources to the server, but it also prevents the disclosure of confidentiality. To log in to X, the user only needs to log in as a command line and type startx to go to the desktop.

Error 5: Free license, because the license is not understood

If the license is not properly configured, it will leave a chance for the hacker. The easiest way to handle licensing issues is to use the so-called RWE methods, namely Read, Write, and Execute. Suppose you want a user to be able to read a file but not a file. To do this, you can execute: chmod u+w, u-rx filename, some new users may see an error saying they don't have permission to use the file, so they use: Chmod 777 filename, thinking that this can Avoid problems. But doing so actually leads to more problems because it gives the file executable permissions. Keep this in mind: 777 gives all users the permission to read, write, and execute a file. 666 gives the read and write permissions of a file to all users, and 555 reads and executes the file. To all users, there are 444, 333, 222, 111 and so on.