Learning Linux from scratch is learning with Marco videos. In order to deepen the memory, convenient for future inquiries, to make a summary of knowledge points. To better automate operations, you must be proficient in using Linux commands. But commands are numerous, and infrequently used will be forgotten. This will require the use of command help.
There are 6 ways to get command help:
No. |
Description |
How to use |
1 |
View command Manuals |
# Man COMMAND |
2 |
View information page (info similar to browse the Web, more comprehensive than man) |
# info COMMAND |
3 |
A brief use of help |
# COMMAND--help |
4 |
See the documentation that came with the name itself |
/usr/share/doc/command-oversion |
5 |
View the official release version of the document |
Www.redhat.com/doc |
6 |
Internet search |
Google |
The first method, relatively simple, check the information is more complete. Here are the main instructions on how to use the Man command manual.
# Man [Chapter (chapter)] <command>
In general, the chapter numbers in the Man command format [] can be omitted. Unless there are special commands you need to enter a chapter number to find. This is because according to the type of command, different types of command help manuals may be in different chapters, the same command can be categorized as multiple chapters, and sometimes you need to enter a chapter number to find the information we need. Let's look at the chapter information that is included.
The Man Handbook is divided into 8 chapters:
Chapter |
Description |
1 |
General user commands. |
2 |
System calls. |
3 |
C-language function library. |
4 |
Explanations for drivers and system devices. |
5 |
Explanation of the configuration file. |
6 |
The command of the game program. |
7 |
Useful miscellaneous commands, such as Macro command packages. |
8 |
Administrative commands about system maintenance. |
Why don't you enter a chapter number when you use the man command normally? That's because we generally find the command in the first chapter, the other Man command is from the lower section to the high section, so you generally do not need to enter the chapter number.
If some of the commands need to be neat, how do we know which chapters have the necessary information? This will use the Whatis command. Format:
# Whatis command: Gets the help document for a command in which chapter
Note: Some help documents are long and the screen is not finished. You need to use the keyboard to manipulate document wrapping, page breaks, and other display actions.
>> Operation shortcut Keys:
-Turn the whole screen: the space bar (flip one screen backward), B (Turn one screen forward);
-Turn half screen: ctrl+d (half-screen backward), ctrl+u (half-screen forward);
-Change one line: Enter the return (one line backwards), K (change one line forward);
-Jump to: g (jump to the end of the file), 1G or G (jump to the file header);
-Exit: Q
>> Text Lookup Method:
/keyword: From the current cursor line, the end of the file to find;
Keyword: from--------------------------first------;
N: The next match in the same direction as the current find command;
N:--------------opposite----------------;
The above is the use of the Man command, write a bit rough, and for the moment will not be a picture. Welcome to guide!
This article is from the "Thought Bike" blog, please be sure to keep this source http://gangan.blog.51cto.com/745672/1414422