How to Learn about linux

Some suggestions for studying linux-general Linux technology-Linux technology and application information. The following is a detailed description. 1. At the beginning, remember more commands. It is best to have a linux Command book. Remember all the commands and do not say that some commands are useless, once your accumulation is profound, you will find that every command is incredibly appealing.

2. You can select your favorite among the systems with up to 5000 commands, and use the most frequently-used commands for yourself. Although it was 5000 at that time, the source code structure of most commands was almost the same. If you imagine the development of programmers, you should familiarize yourself with the commands, you naturally want to know how these programs work, and then you can read the source code.

3. How to find the source code, you can choose sourceforge, one by one, of course, one by one manually. When you get bored, you should learn how to write shell scripts, sf image sites, debian's image site and gentoo's image site help you automate your desired program source code.

4. You can use vc or sourceview to help you read the code. At that time, you had to spend a certain amount of energy, and there should be 10 minutes of preparation time. Once you leave this machine, you can't read the code again. My suggestion is to make it into chm. After you read some code, you can prepare the code at any time, let you check the program where something went wrong. At that time, it was just a general positioning. If it was really difficult to locate the problem, we still had to locate it step by step. For code indexes, you can select global. In addition, if the program in linux has a problem, I can quickly browse the code based on chm and locate the program issue. This should be the way to change the system management from know how to know why.

5. At the end of the day, you will find that the user-level things are too shallow. That is to say, they cannot satisfy your curiosity. That is, no matter how many user-layer programs you have read, you cannot view the program from the underlying point of view. At that time, g ++ was also a user-layer program, but it was still complicated, this is just a question about how software drives hardware. Software Generation is also very complex. algorithms are much more complex than software-driven hardware. At this time, you should be able to look at the kernel code. In fact, at the beginning, you can refer to the kernel code, and the demand drives your learning. I decided the effect is better.

I usually seldom write these things because I think it is a waste of time. I would like to summarize them today and hope to give some inspiration or directions to the future.

Each person has a different way of learning linux, which is for reference only.