Linux Administration is broken down into five broad categories or parts. Chapters are organized under each category so no matter what I was looking for, I found it right at my fingertips. Link
|
|
One of the things I look for in a “beginner's guide” is a well rounded content selection. When I'm trying to learn how to administer Linux, nothing is more frustrating than to pick up a book that's advertised as “a complete guide”, only to discover that either there are holes in the information base or that each subject is treated far too lightly to really learn anything. At first blush, Shah and Soyinka's Linux Administration: A Beginner's Guide 4th Edition is neither of these.
Like most techs, I am a very linear thinker. I like my content to be well organized and easy to find. This is true whether I'm writing the content or reading it. Happily, Linux Administration is broken down into five broad categories or parts: “Installing Linux as a Server”, “Single-Host Administration”, “Security and Networking”, “Internet Services”, and “Intranet Services”. Chapters are organized under each category so no matter what I was looking for, I found it right at my fingertips.
While the book says it's a “beginners guide”, it is not for the absolute newbie. The authors assume that the reader has some network and server administration experience in the Windows world.
In fact, the first chapter is called “Technical Summary of Linux Distributions and Windows 2003” which examines the differences between Linux and Windows .NET Server.
Two major points need to be made about the book at this point. First, it is designed to be read by Windows admins and almost continually compares Linux and Windows server systems throughout the book.
Second, the book has a strong Red Hat/Fedora Core bias. If you are looking for a “pure” Linux book with no mention of Windows, you won't find it here. Also, if you plan on practicing what the book preaches, you'll find it easier to do so on Red Hat or Fedora (I lean towards Debian myself, but I guess you can't have everything). With that said, let's take a look at the book one section at a time.
Link |