The authors have written and constructed this book well to assist an individual in dealing with the problems of managing a UNIX computer installation. They provide the reader with the comfort of knowing that they have faced the challenge of keeping UNIX-based systems running on several different configurations.

The scope of the book is broad, limiting the authors in providing detail that the reader might want. This does not detract from the book’s value, since most individuals who have had some interaction with UNIX have found that some of the joy of UNIX is in discovering things for themselves. The authors do a superb job of starting one off in the correct direction with the hope that the reader will continue his or her pursuit of the subject. The book’s coverage ranges from a modest 3B2 AT&T computer to Amdahl’s machines, with intermediate stops at Sun Microsystems and DEC’s Ultrix.

The book opens up areas for the reader to consider in more depth, such as STREAMS, UUCP, and TCP/IP. The authors show expertise in helping individuals with dilemmas that arise as a consequence of hardware manufacturers’ poor documentation and lack of care for customers.

The book skillfully guides the reader toward UNIX global variables and administrative files that should be looked for and examined. The discussion of adding terminals and the care of disc drives is well done.

The authors make tuning a noble pursuit, with their understanding of how difficult a task this is. They give some warnings about what not to do with start-up systems. The text also gives some warning about what to do when the system crashes and some good hints as to what not to do with certain processes. This topic needs more attention.

The authors stay within the jargon of UNIX (this jargon is perhaps the most difficult thing for me to put up with) and therefore make the text readable to more people. They refrain from generating some understandable commands for their own private use and then giving an explanation of a private cure. They must be applauded for this restraint.

Getting a time-dependent process to operate at a specified date and time using rc on my 3B2 involves more than is stated in the book. A password file is checked to ensure that the user ID is permitted to invoke such a request. The author’s warning regarding deviant systems hardly seems necessary, since dealing with UNIX without proper documentation should be enough for anyone to bear. The book is well suited for those who have not had the luxury of attending expensive tutorial classes explaining the internals. This includes individuals who own a UNIX system but cannot afford these classes.

For software security, the 3B2 has a chip that is in effect a license plate number. Some software manufacturers take advantage of this by referencing this chip to be sure that the software is indeed running on the system for which it was purchased. This practice should be encouraged by administrators, since financially sound software companies will aid the industry.

The book cites valuable references. I sincerely hope that the authors will write a sequel.