Unix/linux System Management Technical manual Read (c)

2016.8.12 23:20-23:50

1.2 Suggested BACKGROUND

1.2 Reader's knowledge background

We assume in this book so you have a certain amount of Linux or UNIX experience. In particular, you should has a general concept of what the system looks and feels from the user's perspective since we do N ' t review this material. Several good books can get to speed; See the Reading list on page 27.

This book assumes that the reader already has a certain program of Linux or UNIX experience. In particular, there is a general concept of the style of the system from the user's point of view, as we no longer review this material. There are some good books to help readers quickly grasp these concepts, see page 27th.

Even in these days of compiz-powered 3D desktops, the GUI tools for system administration on UNIX and Linux systems remain Fairly simplified in comparison with the richness of the underlying software. In the real world, we still administer by editing configuration files and writing scripts, so you'll need to be comfortabl E with both a command-line shell and a text editor.

even on desktop computers with three-dimensional graphical display capabilities today, GUI tools for UNIX and Linux system management are relatively simple compared to their lower-level rich software. In the real world, we still need to edit the configuration file and write scripts to do the administration work, so the reader needs to be accustomed to using some kind of command line shell and some kind of text editor.

Your Editor can be a GUI tool like gedit or a command-line tool such as VI or Emacs. Word processors such as Microsoft Word and OpenOffice Writer is quite different from text editors and is nearly useless For administrative tasks. command-line tools has an edge because they can run over simple SSH connections and on ailing systems that won ' t boot; There ' s no need for a window system. They is also much faster for the quick little edits this administrators often make.

The editor can be a GUI tool like Gedit, or it can be a command line tool like VI or Emacs. Word processing programs such as Microsoft Word and OpenOffice are very different from the wide-text editor and are of little use for system administration. Command-line tools have an advantage because they can be run through an SSH connection and can be used on systems that have problems that cannot be started, and do not require a graphics window system. They run much faster for small editing tasks that system administrators often do.

We Recommend Learning VI (now seen more commonly in its rewritten form, VIM), which are standard on all UNIX and Linux Syst Ems. Although it may appear a bit pallid when compared with glitzier offerings such as Emacs, it's powerful and complete. GNU's Nano is a simple and low-impact "starter Editor" which has on-screen prompts. Be wary of nonstandard editors, though; If you are become addicted to one, you may soon tire of the dragging it along with the install on every new system.

We recommend that readers learn to use VI (now the most common is its rewritten form, VIM), which is the standard software on all UNIX and Linux systems. Although the EMASC with such gorgeous software, vi may appear somewhat dull, but the function of VI is very powerful and perfect. The GNU Nano is a simple, easy-to-start "starter Editor" that features a ScreenTip. Use a nonstandard editor with caution, and if the reader is already "addicted" to such an editor, it will soon get bored because it needs to be brought to the side so that it can be installed on every new system.

This article is from the "Zhao Dongwei blog" blog, make sure to keep this source http://zhaodongwei.blog.51cto.com/4233742/1837474

Unix/linux System Management Technical manual Read (c)