Slashdot Mirror
Linux Network Administrator's Guide, 2nd Edition
This book cleared up many questions I had, enabling my home network to run more efficiently and securely. For example, I learned about many options that can be adjusted in the kernel configuration to allow building a customized kernel which is optimized for your system and needs. This took me one step closer to being ready for my first attempt at compiling my own kernel. I also learned about and implemented some changes to my DNS configuration (improvements to /etc/hosts and /etc/resolv.conf), which resulted in faster name resolutions for web browsers and file managers. I found the information to be detailed enough so that I got what I needed, but not so overwhelming as to turn off my interest level. Another positive note was that the descriptions and examples given throughout the book are "distribution-neutral." I'm using Mandrake 9.1 and RedHat 9, and the configuration file instructions matched up perfectly with both filesystem structures. I believe they would also apply directly to other mainstream distributions, or be easily adapted to slightly different locations.
The book covers some history of networking, and explains the TCP/IP protocol in great detail. Issues covered include IP addressing/subnetting, name resolution, routing, kernel considerations, and drivers. The next several chapters discuss how to configure many kinds of networking hardware and software, such as ethernet, serial/SLIP/PPP, and NIS/NFS. There were great examples of the configuration files that require editing, with understandable explanations of why you were doing it. A make-believe small business is used as an example throughout the book, as they build and expand their corporate network and integrate with other branches of the company.
The next section covered how to set up a firewall/router, again with great example configuration files and scripts. This part went into just the right amount of detail, and included discussion on packet filtering, firewall testing, IP packet accounting, and NAT/masquerading. I'd say I got the most amount of useful knowledge from this section, and will refer to it many times again when I get around to building a router for the home LAN. I now feel that I have enough knowledge to replace my LAN's commercial router with an older computer I have laying around, running Linux with a customized iptables firewall. The IP/packet logging and accounting procedures I now understand will make me feel much more comfortable with what's going on in my network, and the security issues involving the internet interface.
There are several chapters dedicated to setting up and understanding various network services that you may with to install and administer. These include email server/client, UUCP/Usenet news, NNTP and INN, and DNS. There are excellent diagrams, tables, and examples throughout the book. If there was one area I would have liked to have seen addressed (maybe in the next edition?), it would be to have at least an introductory chapter addressing the use of Samba, as it is a common, easy method of integrating a Linux network with Windows computers. Overall I was very pleased with the book, and would recommend it to anyone interested in Linux networking. It has something for everyone, at all skill levels. The table of contents and index are excellent, and you can find exactly what you're looking for very quickly. Additionally, the book offers an excellent list of other reference books, websites, newsgroups, and user groups to assist with getting more in-depth information. I'd like to extend a "well done" to the authors, and to O'Reilly Publishing!
You can purchase the Linux Network Administrator's Guide, 2nd Edition from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page. Dan Clough suggests you visit the Pensacola Linux User's Group, too ;)
I have never liked this book. It does a great job of telling me things I don't need to know.
I wish I had only spent my money on Essential System Administration, 3rd edition (Frisch), rather than both.
It should be the running theme with Linux:
Linux Network Administrators Guide 2nd ed
O'Reilly Linux Command Reference
As far as "networking for linux", I wouldn't put any of those computers "online" without something else between them and the internet. Like a linux box running a BSD, Slackware, or Debian. The overhead and unneccessary packaging for those systems makes it an internet nightmare.
You're right you know "enough to be dangerous" as in getting some worm and unknowingly using your computer as the host of a DDoS attack.
Ignore the "p2p is theft" trolls, they're just uninformed
Having read this book I can tell you that it is NOT really for beginners. You may want to try Essential System Administration , which is also by O'Reilly .
As part of O'Reilly's Open Books Project, this book is also available (without the shiny binding) for free. You can also pickup PDF's and the like the Linux Documentation Project's guides section.
Christian Jones
Medicine. Mathematics. Mediocrity.
from the review I can say that these are the negatives:
.02 on a poorly written, FUD article.
Too general (no Samba, very light on DNS, and nothing about anything terribly important [ie Squid])
WEAK on DNS (who doesn't know about the "changes that make resolving hostnames faster"?)
If it's easy enough for Mr. I run RH9 and Mandrake9 you know it isn't in depth enough to be considered a "Linux Administrators Guide vol. 2"
Wow, helped with iptables and NAT/Masq. The HOWTOs are VERY thorough and easy to understand (nevermind the fact that they are free).
Just my
Instead of the Barnes and Noble link...get it here for almost 40% less:
Bookpool
I have this book as well, and do not share the reviewer's enthusiasm for it, on several points.
1. It is old (2000, original edition is 1995) and vast sections of the book are completely useless.
2. It is too concise. The sections on NAT and Firewall are vague, and i had to consult additonal resources just to figure out how to get it to work. I had the same problems with the DNS chapter and the NIS chapter. This book gives enough info to let you know what something is, but often not enough to serve as a useful reference. The authors encourge you to buy additional o'reilly books if you want to know more, which is annoying.
3. Important stuff is missing. SSH? nothing. SAMBA? nothing. Entire chapters dedicated to obsolete technologies like PPP, SLIP, IPX, and UUCP? lots.
4. This book did not need four chapters on how to setup a Usenet news server. What a waste!
Although I was a newbie when I first read it, and learned a lot, i would recommend people look elsewhere. This book is simply too out-of-date. Half of it should be omitted, and the other half expanded so as to become usable.
I'd don't know my skill level with Linux and networking versus the reviewer, but I'd fall into the category of "just enough knowledge to be dangerous".
/etc/hosts file and be done with it. Do you really need a DNS server for that? And if you REALLY need critical DNS, do you want to use a "survey book" to set-up the configuration! Please! The hosts file is about the extent this book should go with DNS as far as I'm concerned.
Frankly, there are negatives to this book. A few examples I can think of off the top of my head (unfortunately, I don't have the book in front of me to refresh my memory) are:
Generally, no matter what topic in the book, all you get is a simple walkthrough of the commands and minimal description of why you do them or what to do for an unusual set-up. Well, ok, I understand it is "survey type" book, but since all this stuff is readily available via man pages, How-Tos and newsgroups, why buy a 40 dollar book on it?
For example, getting an ethernet adapter configured via the command line was easy to do, but hard to follow in the book as to why you use certain commands and flags and what things other than the simple example they are good for. I didn't get a great explanation as to theifconfig command and the route command. Also, it was difficult to understand how to configure two ethernet adapters on the same machine in order to set up a Linux firewall or DHCP server in place of a router.
The section on DNS is a big waste of time. If you are going to delve into DNS, you might as well get O'Reilly's DNS & Bind and slog through that nightmare (not the book, setting up DNS). If all you are doing is setting up 5 machines behind a home router (my set-up is similar), then just use the
I'd say the same for setting up a mail server... with all I hear about sendmail, why would I count on the simplistic outline in a general Linux networking book for configuring sendmail? Especially with the chance of screwing it up and having all hell break loose with the mail server and my network!
It is not a worthless book. It does a good job of explaining how the internet works, how you set-up a machine to be on the internet and what general security issues are involved (i.e., enough for some clown like me to keep his network safe behind a home router or even behind linux router if you slog through setting that up).
I won't pretend to be a professional IT guy. But I do like playing around with home networking using various services for fun, so when I buy a book like this, I'd like it to contain more than just simple examples and a rehash of readily available stuff from man pages and How-Tos.
-Anthony
While I worked some on this O'Reilly's open book policy and am proud to see it growing, I also should admit for historical accuracy that the Linux Network Administrator's Guide started as an LDP project. I made a deal with Olaf Kirch, the first author: O'Reilly would put in a lot of editing and production work and donate it all back to the free version of the book, and in return we'd publish it. The license has changed over time, but the book started out open and has remained that way. Nevertheless, I and the rest of the company invested a lot of time and money into making it a strong, professional text.
Hey! I already reviewed this book. Right here on slashdot. Almost three years ago.
Oceania has always been at war with Eastasia.