Shulou(Shulou.com)06/03 Report--

23:20-23:50 on August 12, 2016

1.2 SUGGESTED BACKGROUND

1.2 the reader's knowledge background

We assume in this book that you have a certain amount of Linux or UNIX experience. In particular, you should have a general concept of how the system looks and feels from the user's perspective since we don't review this material. Several good books can get you up to speed; see the reading list on page 27.

This book assumes that the reader already has Linux or UNIX experience in certain programs. In particular, it is necessary to have a general concept of the style of the system from the user's point of view, because we no longer review this material. There are some excellent books that can help readers grasp these concepts quickly, please see page 27.

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 comfortable with both a command-line shell and a text editor.

Even on today's desktop computers with three-dimensional graphics display, the GUI tools for UNIX and Linux system management are still quite simple compared with the rich software in their lower layers. In the real world, we still have to edit configuration files and write scripts to do the administrative work, so readers need to get used 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 are quite different from text editors and are nearly useless for administrative tasks. Command-line tools have 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 are also much faster for the quick little edits that administrators often make.

The editor can be a GUI tool like gedit or a command-line tool like vi or emacs. Word processors such as Microsoft Word and OpenOffice are very different from extensive editors and are of little use for system administration. Command-line tools have an advantage because they can be run over a SSH connection and can be used on systems that cannot be started when something goes wrong; and there is no need for a graphical window system. For the tiny edits that system administrators often do, they also run much faster.

We recommend learning vi (now seen most commonly in its rewritten form, vim), which is standard on all UNIX and Linux systems. Although it may appear a bit pallid when compared with glitzier offerings such as emacs, it is powerful and complete. GNU's nano is a simple and low-impact "starter editor" that has on-screen prompts. Be wary of nonstandard editors, though; if you become addicted to one, you may soon tire of dragging it along with you to 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 vi may seem a bit dull compared to gorgeous software like emasc, vi is still very powerful and perfect. GNU's nano is a simple, easy-to-use "getting started editor" with on-screen prompts. Be careful with non-standard editors. If readers are "addicted" to such an editor, they will soon get tired of it because they need to bring it with them so that they can be installed once on every new system.

August 13, 2016 23:00-23:40

One of the mainstays of administration (and a theme that runs throughout this book) is the use of scripts to automate administrative tasks. To be an effective administrator, you must be able to read and modify Perl and bash/sh scripts.

One of the main pillars of system management (and a theme throughout the book) is the use of scripts to automate administrative tasks. To become an efficient system administrator, you must be able to read and modify Perl and bash/sh scripts.

For new scripting projects, we recommend Perl or Python. As a programming language, Perl is admittedly a bit strange. However, it does include many features that are indispensable for administrators. The O'Reilly book Programming Perl by Larry Wall et al. Is the standard text; it's also a model of good technical writing. A full citation is given on page 27.

For writing new scripts, we recommend using Perl or Python. Perl is a bit strange as a programming language, but it does contain many features that are indispensable to administrators. Programming Perl, published by O'Reilly and written by Larry Wall et al., is a standard tutorial for Perl. It is a model of technical books, and the 27 pages of this book give more complete information.

Many administrators prefer Python to Perl, and we know of sites that are making a concerted effort to convert. Python is a more elegant language, and Python scripts are generally more readable and easier to maintain. (As Amazon's Steve Yegge said, "The Python community has long been the refuge for folks who finally took the red pill and woke up from the Perl Matrix.") A useful set of links that compare Python to other scripting languages (including Perl) can be found at python.org/doc/Comparisons.html.

Many system administrators prefer to use Python rather than Perl, and we know that there are places that are working together to move from Perl to Python. Python is a more beautiful language than Perl, and Python scripts tend to be more readable and easier to maintain (as Amazon's Steve Yegge puts it, "the Python community has long been a refuge for people who escaped from the Perl camp, who swallowed red pills and woke up from Perl's Matrix.") You can find a set of useful links from python.org/doc/Comparisons.html to compare Ptyhon with other scripting languages, including Perl.

Ruby is an up-and-coming language that maintains many of the strengths of Perl while avoiding some of Perl's syntactic pitfalls and adding modern object-oriented features. It doesn't yet have a strong tradition as a scripting language for system administrators, but that will likely change over the next few years.

Ruby is a rising language. It retains many powerful functions of Perl, avoids some grammatical defects of Peral, and adds modern object-oriented features. As a scripting language for system administrators, it is not deeply rooted, but that may change in the next few years.

We also suggest that you learn expect, which is not a programming language so much as a front end for driving interactive programs. It's an efficient glue technology that can replace some complex scripting. Expect is easy to learn.

We also recommend that readers learn expect. It is not so much a programming language as a front-end language for driving the execution of interactive programs. It is an efficient "glue" language that can replace some complex scripting, and expect scripts are easy to learn.

Chapter 2, Scripting and the Shell, summarizes the most important things to know about scripting for bash, Perl, and Python. It also reviews regular expressions (text matching patterns) and some shell idioms that are useful for sysadmins.

Chapter 2 of this book summarizes the most important knowledge about bash, Perl, and Python scripting. This chapter also reviews regular expressions (text matching patterns) and some idioms of shell, which are useful for managing work with the system.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.