UNIX Hints & Hacks
Introduction
|
Sections in this Chapter: |
|
|
|
|
|
|
||||
|
|
||||
|
|
||||
|
Before Beginning |
|
|||
|
|
||||
|
|
|
|
|
UNIX Hints & Hacks |
|
||||||||||||||||||||||||||||||||||||
|
Introduction |
|
||||||||||||||||||||||||||||||||||||
|
No two computing environments are ever exactly alike. System administrators have individual techniques for administering the operating system, patches, and various software applications. Every environment has or should have a set of procedures in place for implementing new files, applications, or programs. When all this is put together, no two computing environments are alike. This is why all the examples discussed in this book should be fully tested and executed within a development environment before they're implemented in a production environment.
Hacks discussed in the book deal with the modification, manipulation, and even removal of key UNIX files. There are examples of truly dangerous superuser commands that can cause severe damage in a production environment if they're used incorrectly. Some of the hacks discussed might not be the most efficient, but these hacks can provide insight to applying the hack to other situations, in which it is more efficient. Because there are several ways to perform a specific task, more than one way might be discussed. Although some of the hacks discussed might not be the most efficient way to handle a situation, the point is to show various ways the hack can be executed.
|
UNIX Hints & Hacks |
|
||||||||||||||||||||||||||||||||||||
|
Introduction |
|
||||||||||||||||||||||||||||||||||||
|
© Copyright Macmillan USA. All rights reserved.