I'm not a Linux admin, I like to think of myself as a experienced Windows admin who uses basic troubleshooting skills to under stand Linux. I have worked with Bind and done basic administration on Linux desktop and server level, also using Linux at home. When I was researching books to learn more about Linux I found that many books fit into two categories, either they were extremely simple, demonstrating how to use the desktop or they were extremely complex, showing every little detail of the Linux operating system.
While I understand learning from the ground up is helpful, I prefer to have a server up and running, then reverse engineer the applications how it works. For me it's much more fun to have a working model than just read about it on paper. I like to have it running, then make changes, and if it breaks the system go back and see what caused it. Maybe it's my Windows experience but I like to work more on the maintenance and administration issue than battle issues installing an application.
On this point, I searched and found by chance the Official Ubuntu Server Book at a local store. Since I was looking for more information about Ubuntu, and already had a few other books on RedHat or CentOS, I was interested how well this book would compare to the others and if it would be too technical for me.
After reading a few chapters I was sold and ended up ordering it shortly after from Amazon. What I really liked about this book is extremely clear and easy to read, which is a refreshing change from the typical Linux/UNIX book. This book is really how I would write a book for system administration. The first chapters deal with the basics of a Linux system, such as installation and essential system administration. These chapters cover the history of Ubuntu, disk partitioning, base package installs, but each topic is covered with enough information to get you started but does not go too far in depth to dwell on the subject too long. Basically, even for the new Linux user, it should be enough to get you started.
Moving on the chapters cover package management, automated Ubuntu installs, common Ubuntu servers and security. Again the topics are covered with good amount of details but as the book is a more focused on the server not a specific function, the information is enough to start you on the right path. One of my favorite chapters is number 6, security. I really enjoy the reading of this chapter as it reads like a seasoned sysadmin giving me information rather than an engineer explaining it with technical terms. The firewall information was helpful, I had problems in the past configuring this and the extra notes included help with real world experiences.
I should also mention that chapter 11, troubleshooting should be a must read for any system administrator or system user even if you do not work with Linux professionally. The details of how to "divide the problem space" are not isolated only to Linux but can help any one from network devices to casual Windows users. It's often very difficult to teach troubleshooting but the book gives a excellent intro and basics on how to use the tools correctly. The authors describe in what order you should perform each task, using tools to confirm you have connectivity, DNS is working, etc. Also they give basic foundation on trouble shooting, especially the golden rule of Linux, "reboot as a last resort". :)
This book was really the first book I found that explained how to install Bind and add a slave server within a page or two, where other books would give only a paragraph if that. I keep this book on my desk and thanks to the great writing, I'm deploying 10.04 LTS servers for our DNS Bind refresh project.
In closing, I should also mention that I met the co-author Kyle Rankin at a local Linux user group meeting here in the SF Bay Area. He gave a discussion about troubleshooting and after was very helpful when I asked a question about a complete DNS issue I encountered. It's great to see a author who is not only a great writer but also active in the Linux community.
