True feelings of Linux beginners

I am about to become a senior vice president. linux started to contact me two years ago. now I think that I am not a qualified operator. My goal is to truly learn how to work efficiently in linux. I want to talk about my views on linux learning from these days. I declare in advance that I am a Cainiao, individual

I am about to become a senior vice president. linux started to contact me two years ago. now I think that I am not a qualified operator. My goal is to truly learn how to work efficiently in linux. I want to talk about my views on linux learning from these days. I declare in advance that I am still a Cainiao. I personally hope that I will not mislead beginners and hope that I will be more accurate.
I first came into contact with linux in the next semester of my freshman year. the reason why I got in touch with linux was completely blown by the linux hot air of the year. at that time, some people thought that windows would soon be over when linux was born. Later facts prove that the hot air of linux is indeed amazing, and linux has made great strides, but windows has not been fully played, because windows is also improving. At that time, without my own computer, I could only read books, but I had little knowledge about computers, and I could not do anything practical. when I read these books, it was like talking about them on paper (such as processes, shells, api ). But I had to admire the Finnish Richard Matthew Stoman. I went to the library and read a lot of information to find out why he was a great organizer and planner, it is mainly engaged in the development and maintenance of the kernel of the operating system. many other software of the operating system is released through the GPL convention. without these software, linux will not have today's achievements and Halo. Then they began to pay attention to the linux development team. they claimed to be "hackers" in the true sense, and explained their work purpose with the phrase "hacker construction and hacker destruction. At that time, I also read a book written by a hacker named "How to be a hacker". the point in the book was admirable. I copied it and copied it again as follows:

If you want to be a hacker, read the following things until you believe them:

1. The world is filled with fascinating issues to be addressed. Being a hacker has a lot of fun, but it takes a lot of effort to get fun. These efforts require motivation. Successful athletes get motivation from the pleasure of exercising and exceeding their limits. Similarly, as a hacker, you have to have basic fun solving problems, honing your skills, and exercising your intelligence. If you are not a natural hacker and want to be a hacker, you must try to become such a hacker. Otherwise, you will find that your hackers' enthusiasm will be swallowed up by other distracting things, such as money, sex, and social virtual names. Similarly, you must build enough confidence in yourself-believe that, even if you have almost no idea about a problem, as long as you experiment and study at 1.1 points, you will eventually master and solve it.

2. A problem should not be solved twice. Smart heads are precious and limited resources. When the world is still filled with a lot of interesting new problems to be solved, they should not be wasted on re-inventing things like wheel. As a hacker, you must believe that the time for other hackers to think is precious. Therefore, sharing information, solving problems, and publishing results to other hackers is almost moral, in this way, other people can solve new problems rather than constantly dealing with old problems. You do not have to think that all your inventions and creations must be published, but the hackers who do so are the ones who win everyone's respect. Selling money to support your family, renting a house, buying a computer, or even making a fortune is also compatible with hacking values. The key is that you should never forget that you are a hacker.

3. Boring and boring work is evil. Hackers (generally creative people) should never be troubled by stupid repetitive labor, because when this happens, it means they are not doing what they can only do-to solve new problems. This waste hurts everyone. Therefore, boring and boring work is not only uncomfortable, but also evil. As a hacker, you must firmly believe this and automate as much boring work as possible, not only for yourself, but also for others (especially those hackers ). This is an obvious exception. Hackers sometimes do repetitive or boring work in the eyes of others for "mental rest", or to acquire certain skills or special experience that is not otherwise available. But this is voluntary-people with brains should not be forced to do boring work.

4. Long live freedom. Hackers are born anti-authoritarian. Anyone who can send commands to you can force you to stop solving the problems you are fascinated by. at the same time, according to the general idea of the dictatorship, he usually gives some extreme ignorance reasons. Therefore, wherever it is, any authoritarian practice, as long as it oppress you and other hackers, you will fight against it to the end. This is not a challenge to all authorities. Children need to be monitored and criminals need to be taken care. If the command is executed to get something that saves more time than other methods, hackers can agree to accept some form of authority. However, this is a limitation. you should not agree to give personal obedience to the authority of intentional transactions. The authority prefers review and confidentiality. They do not trust voluntary cooperation and information sharing-they only like the so-called "cooperation" controlled by them ". Therefore, as a hacker, you have to have an instinctive hostility towards censorship, confidentiality, and the use of force or deception to oppress people with the ability to do so. At the same time, you must be willing to fight for this belief.

5. Attitude cannot replace ability. As a hacker, you must cultivate these attitudes. But with these attitudes alone, you cannot be either a hacker or a sports player or rock star. Being a hacker requires intelligence, practice, dedication, and hard work. Therefore, you must learn to doubt and respect all kinds of abilities. Hackers will not waste time on people who do the same for their models, but they respect those who have the capabilities of a few people, of course, it is best to have mental, technical, and focused abilities. Dear ability, you will enjoy the pleasure of improving your abilities-hard work and dedication will become a high degree of entertainment rather than a hard job. It is important to become a hacker.

If you read these paragraphs over and over again, you will admire them for their "hacker spirit. If you use these attitudes in your life, why is it not the right path. In short, I learned these theories when I was a freshman. I didn't really touch linux at all, but I really wanted to live in linux. I bought a computer when I was in my sophomore year. After I became familiar with windows xp, I began to think about installing linux. At first, I chose the installation CD attached to the school books. at that time, it was red hat linux6.2, which was not successfully installed several times. later I opened the book and vaguely realized that the version was old and the driver couldn't keep up with me, I finally bought red hat linux 9 from the stalls selling CDs in Guilin. Because I have read a lot of instructions on partitions before, and the result is that after I use partion magic 8 to re-adjust the partitions, the installation is successful. at that time, I chose to install all the partitions, it occupies more than 5 GB of space. But after I installed it, I found a book about linux and suddenly found that I didn't know what to do with him, because there was no network (the campus network of the school could not touch it, it is said that I went out for several pieces of news a day, because traffic-based charges are too expensive and there are many animations on the webpage ). I went to the book about linux shell commands and I was not interested after the operation. I suddenly realized how to fix this problem in linux? At that time, I also learned c programming in linux. How did I find it so cumbersome? (this idea was changed when I learned more things, linux c programming is indeed very successful, because he has established a wealth of function libraries, saving a lot of repetitive work ). I personally think that desktop is really useless (there was no network at that time, and there was no need to look at the web page). I opened the graphical interface and started a terminal to input commands. Although I had a network in my sophomore year next semester, I learned the software protel required by my major at that time. it was very difficult to learn only one protel, so half a year has passed.

I always believe that linux is my favorite and cannot forget the book. In my junior year, I took the computer level 4 test. although it was just a summer vacation, I felt that I had gained a lot and had a general understanding of the computer science. I don't think I would take a look at discrete mathematics if it wasn't for the exam. The Theory of compilation principles and relational algebra seems unrelated to computers and closely related to mathematics. After reading these theories, I realized that I had to look down on computer science before. This semester, the major is those electrical and electrical appliances, which seem very simple, so I didn't have to look at them and began to take the initiative to learn computer things. I learned a little about everything, but I didn't know it. At this time, I didn't actually learn much about linux, that is, I installed various versions of linux on my computer and compared which one is suitable for myself. I came to the conclusion that none of them are suitable for me, I have to adapt to them. They have their own strengths. in the next semester, they will start to learn the single-chip microcomputer and PLC programming that requires continuous jump. at that time, they thought it would be nice to program like c. I started to learn c ++ at the guidance of a certain expert, because I carefully learned SCM programming and PLC programming, so I didn't learn much about linux, people started to get in touch with debian and freebsd. I personally feel that these two systems belong to the very "deep" system, which is simple, a little progress, and never make any radical moves. I admire the network installation methods of these two systems. if there is a good network connection, you can install what you need, you only need one apt = get to easily install and uninstall the management software package. After reading the article "working entirely with GNU/LINUX", although there are many radical ideas in it, I think he spoke of the main reason for working with non-windows: The pursuit of efficiency. An important part of this process is as follows. I think it is a good illustration of The KISS (keep it simple, stupid) principle:

The perfect combination of various applets is the most important feature of UNIX. it is the idea of UNIX design. Let each program have only one dedicated capability, and then let them cooperate. Xwindow also inherits this good tradition. This is probably the end of Windows and other operating systems. The unity of UNIX Programming and the perfect combination are incredible! Shell, grep, find, awk, sed, make, Perl, Emacs, vi, tin, Mutt, they are so consistent! Once you have learned the regular expression of sed, other programs can basically use it. Once you have learned vi and VIM, you will find that their operations are so regular. it seems that vi designers have designed VIM decades ago, A perfect and unified operation method! Vi operations are also reflected in Mutt, tin, and many other programs. You can even set bash to vi to input command lines. that's what I do. A program can call another program to obtain data. it can hand over the data to it for processing and return it. it can "embed" another program in its own window. In Windows and other non-UNIX operating systems, such cooperation is very difficult. I used Perl in Windows for some automatic work. However, in Windows, the file operations and pipelines are so unstable that programs cannot work together. You don't want to embed the UltraEdit editor in the Visual Studio window. you don't want to use a login Ct script to control telnet to Shuimu Tsinghua BBS. Windows applications are large and comprehensive, large and complex. all email programs need to provide their own editors, send and receive emails themselves, and display their attachments. Each BBS program provides its own Virtual Terminal and communication code. Each IDE provides its own editor, compiler, assembler, and debugger. In order to use a new program, people need to adapt to all the interfaces provided by it, instead of using the key binding and menu organization of their favorite editor ...... Cannot be DIY!

All right, the two articles I have quoted have clearly explained some of my feelings, so I won't be able to make an axe in front of many senior people. although the language is simple, it is indeed mine.