Slashdot Mirror


FreeBSD: The Complete Reference

Just Some Guy writes "I recently received a promotional copy of Roderick W. Smith's "FreeBSD: The Complete Reference". I was pretty skeptical at first - it's my nature - but was pleasantly surprised at the range and depth of information presented in a very accessible format. While not ready to supplant Greg Lehey's "The Complete FreeBSD", it's certainly a worthwhile read for new and moderately-experienced users." Read on for Just Some Guy's full review. FreeBSD: The Complete Reference author Roderick W. Smith pages 869 publisher The McGraw-Hill Companies rating 9 out of 10 reviewer Kirk Strauser (Just Some Guy) ISBN 0072224096 summary (Most) everything you need to know about FreeBSD

Overview

This is a large book. At 869 pages, not including copies of the GPL and BSD License, it packs some serious heft (it weighs slightly more than three pounds).

It is divided into six main parts, which are further divided into 32 (!) chapters. The sections are:

  1. FreeBSD Installation: Hardware requirements, installation instructions, and a general overview.

  2. Basic System Administration: Partitioning, startup procedure, file management, printer setup, user management, software installation, kernel configuration, and X.

  3. Network Configuration: Introduction to networking, dial-ups, client/server principles, basic firewalling.

  4. Servers: In-depth explanation of file, mail, web, and shell servers, plus an overview of DNS, NTP, DHCP, and other random services.

  5. Common User Programs: Introduction to KDE and GNOME. An overview of various network clients and office software. A short tutorial on The GIMP. The state of multimedia and games on FreeBSD.

  6. System Maintenance: The basics of system monitoring. How to upgrade the OS and installed software. An overview of system security. How to compile software. Basic scripting. Troubleshooting and how to get help.

The Good

This book is an excellent starting point for people new to FreeBSD, or even to Unix-like systems in general. Each of the wide range of topics is covered in a reasonable amount of detail. Mr. Smith claims to have been working in the field for quite a few years, and it shows in the way each part of the OS is presented as a component of the whole. This isn't a "cookbook"; readers are introduced to each subject in a way that encourages them to make their own configuration decisions.

I was unable to find any factual errors, and I certainly looked for them. The author and proofreaders did a good job of checking their information before going to print. Since my copy was from the first printing, I'm especially impressed.

New users, in particular, will appreciate the hand-holding approach of the earlier chapters on installation and basic configuration. More experience administrators should be able to find enough new information about rather routine subjects to keep them interested.

Of particular interest was the almost complete lack of FreeBSD advocacy in the book. The introduction features a remarkably even-handed discussion of its relative strengths and weaknesses compared to other Unix and non-Unix operating systems. I greatly respect the author's decision to weigh the alternatives fairly and let the reader form his own opinion.

The Bad

FreeBSD: The Complete Reference is, unsurprisingly, a new entry in Osborne's "Complete Reference" series. As such, it's fairly comparable in size, layout, and scope to other books in the series such as Herbert Schildt's C++: The Complete Reference (my favorite C++ text). That's a pretty high standard to live up to, and I began my first pass through the book with a very critical eye.

My only real complaint is that, despite the title, this is not a "complete reference." Although The GIMP enjoys its own sub-chapter, the book makes no mention of certain high-profile features such as Vinum (FreeBSD's logical volume manager) or jails (chroot on steroids). It's obviously not possible to document every single component of the entire OS, but the name would seem to claim exactly that. Of course, even though FreeBSD: The Desktop Reference or FreeBSD: Reference For Users might be more appropriate, those would violate the series' naming convention. Still, don't be fooled by the title.

Although less important, every user has their own idiosyncratic ways of accomplishing certain tasks, and I tend to get distracted by recommendations that are counter to my preferred methods. Having said that, Mr. Smith makes some strange recommendations, such as editing the passwd file and compiling the password database afterward by hand rather than using vipw. His system certainly works, but I can imagine a new user scratching their head in puzzlement at the amount of work necessary to change their name.

The Ugly

Any book of this size and scope will have a few minor quirks, and this is no exception. For instance, the author needed to use several domain names as examples throughout the book. Rather than using the traditional "example.com," he decided to use his own creations. That in itself is no problem, except that he and his publishers have not registered those domains for their own use. I can only imagine the surprise when a curious newbie tries to access one of the hostnames in a web browser and finds that a prankster has register the domain and used it to mirror goatse.cx.

A more serious lapse, in my opinion, was the decision to include an installable copy of FreeBSD 5.0 on the CD that comes with the book. Unfortunately, freebsd.org refers to that version as a "new technology release," and it suffers from a rather long list of installation and stability problems. Some day in the future, the 5.x series will be considered stable and ready for use on production systems, but that's still a while off. I sincerely hope that no would-be new users become disillusioned with their newly-installed systems and give up on FreeBSD as a slow and unstable OS. Despite the drawbacks, though, I can understand the author's desire to focus on the new 5.x series instead of the more stable but older 4.x line. This book was published in 2003, and I doubt that he wanted to have to publish a second edition detailing the new release less than one year after initial release.

Summary

This is a good book with a lot of solid information for new and experienced users. It may have a few minor problems, but it is a well-written and approachable reference that should make a valuable addition to any FreeBSD administrator's bookshelf. I would recommend it highly to anyone migrating from other Unix-like systems, finding themselves in charge of a small network, or wanting to see what the fuss is all about. If you're a new user, though, do yourself a favor: download and install FreeBSD version 4.8 from http://www.freebsd.org/ instead of installing the copy on the book's CD.

You can purchase FreeBSD: the Complete Reference from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

16 of 153 comments (clear)

  1. The thing I didn't like by Anonymous Coward · · Score: 5, Funny

    Was the last line in the book:

    "*BSD is dying."

    It just seemed so out of place.

  2. but ... but ... by B3ryllium · · Score: 3, Insightful

    If the book is half-decent, it will show users how to make buildworld; make buildkernel; make installkernel; make installworld - with whatever the latest codebase might be.

    Therefore, the argument that the 5.0 CD will be out of date is moot - at least for people who have internet connections. :)

    1. Re:but ... but ... by Just+Some+Guy · · Score: 4, Insightful

      True, but you have to get it installed in the first place. 5.0 simply won't boot on some systems. An expert could probably work around the problems, but that's not the target audience of the book.

      --
      Dewey, what part of this looks like authorities should be involved?
  3. The GIMP? by Lerxst+Pratt · · Score: 5, Insightful

    What is the GIMP doing in a BSD Reference book?!? Seems like fluff to me. Especially when you can download a pretty comprehensive GIMP manual online.

  4. Skeptical by dfn5 · · Score: 4, Funny
    I was pretty skeptical at first -

    But then I thought "Hey, the book was free, what the hell do I care?"

    --
    -- Thou hast strayed far from the path of the Avatar.
  5. Thanks for hijacking my referral links by Just+Some+Guy · · Score: 5, Interesting
    The review I originally posted had links to my bn.com referral:
    The book is available from the usual sources. If you want to be nice to me, you can buy it through my Barnes&Noble referral link. If you find those offensive or otherwise objectionable, you can go straight to it.

    I didn't write the review to make money, but it still seems kind of sneaky to replace my referral with Slashdot's own.

    --
    Dewey, what part of this looks like authorities should be involved?
    1. Re:Thanks for hijacking my referral links by Just+Some+Guy · · Score: 3, Informative

      I never said I wasn't going to collect, just that it wasn't the reason I wrote the review. Think of it as seeing a Free Software project page with a PayPal tip jar. The author probably isn't really expecting to make money, but they won't turn it away.

      --
      Dewey, what part of this looks like authorities should be involved?
    2. Re:Thanks for hijacking my referral links by fobbman · · Score: 4, Insightful

      So the /. editors won't fix spalling erorrs in a post but they'll make sure to rip off the referral purchase? Smooth.

    3. Re:Thanks for hijacking my referral links by _xeno_ · · Score: 3, Insightful
      I quick look through other book reviews find that most of them contain a Slashdot link at the end:
      $AUTHOR is the author of $OTHER_REVIEWED_BOOK. You can purchase $BOOK from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

      The first sentence only applies to authors who have already been reviewed on Slashdot, but with very few exceptions (of which Dancing Barefoot, the review immediately prior to this, is one), Slashdot adds the buy link to bn.com as shown in the little template above. I don't think this was anything against you - it's something they do for all book reviews.

      Whether or not it was the right or moral thing to do, I won't judge. Just that it isn't anything against you specifically, it's just part of the standard book review template that Slashdot uses.

      --
      You are in a maze of twisty little relative jumps, all alike.
  6. Re:But the real question is by TheRaven64 · · Score: 4, Interesting
    Actually, the real question is 'is there actually a need for such a book?'

    The first thing I noticed comming to FreeBSD from Linux was the high quality and large quantity of official documentation provided. While I did buy a book when I started off with Linux, I really didn't need to for FreeBSD. This may be because I was already familiar with *NIX by that point (although FreeBSD 'feels' a lot tidier in terms of layout - 100% subjective, your milage may vary). On the other hand there was a large amount of documentation aimed at neophytes which I skipped.

    --
    I am TheRaven on Soylent News
  7. Bullschildt by AltControlsDelete · · Score: 5, Informative
    I question the credibility of any reviewer who refers to something written by Herb Schildt as his favorite C++ text. Good grief.

    From the alt.comp.lang.learn.c-c++ faq:
    16: Why do many experts not think very highly of Herbert Schildt's
    books?

    A good answer to this question could fill a book by itself. While no book is perfect, Schildt's books, in the opinion of many gurus, seem to positively aim to mislead learners and encourage bad habits. Schildt's beautifully clear writing style only makes things worse by causing many "satisfied" learners to recommend his books to other learners.

    Do take a look at the following scathing articles before deciding to buy a Schildt text.

    http://www.lysator.liu.se/c/schildt.html
    http://herd.plethora.net/~seebs/c/c_tcr.html

    T he above reviews are admittedly based on two of Schildt's older books. However, the language they describe has not changed in the intervening period, and several books written at around the same time remain highly regarded.

    The following humorous post also illustrates the general feeling towards Schildt and his books.

    http://www.qnx.com/~glen/deadbeef/2764.html

    Th ere is exactly one and ONLY one C book bearing Schildt's name on its cover that is at all recommended by many C experts - see Q 25.
  8. Does it apply to OS X? by ascii · · Score: 3, Insightful

    Forgive me if this is a dumb*ss question, but can anyone tell me how well it applies to Mac OS X?

    Thankyou.

    --
    naah sig schmig
    1. Re:Does it apply to OS X? by Just+Some+Guy · · Score: 3, Informative
      can anyone tell me how well it applies to Mac OS X?

      Almost not at all. Large sections involve installation and low-level configuration, which is irrelevant for Mac OS X. Ditto for the ports collection, administering the system, upgrading software, or installing multimedia programs. I don't think there's really anything in their for Mac users, other than maybe the section on configuring servers, and Apple probably has their own tools for that.

      --
      Dewey, what part of this looks like authorities should be involved?
  9. include news and deep-documented stuff by LastCa_ · · Score: 3, Interesting

    I've seen a lot of cool stuff to do with FreeBSD (like tweaking the kernel) that was only documented directly into the system (like in the source or man pages) and in some newsgroups.

    My point is, I would be happy if someday, a real "complete reference" book on FreeBSD is created, will all the tweaks and tricks (aka not only a beginner oriented book). No more search in the news and printed-two-years-ago-obscure-documentation for me.

    This is the kind of book I'm looking forward to.

    --
    - LastCall_
    1. Re:include news and deep-documented stuff by Just+Some+Guy · · Score: 3, Informative

      You're looking for Greg Lehey's The Complete FreeBSD, I think. The latest version came out this month.

      --
      Dewey, what part of this looks like authorities should be involved?
  10. VINUM not mentioned = good by Lew+Payne · · Score: 5, Interesting

    "...the book makes no mention of certain high-profile features such as Vinum (FreeBSD's logical volume manager)..."

    Why should it make mention of something that is being phased out of FreeBSD? Anyone who has followed the developers' thread knows that the code for vinum is unmanageable and horribly inefficient, and is being replaced. Why should the book's author teach you about something you should not use and that will be deprecated? Why didn't the reviewer research his comments a bit more before being critical of a positive feature of the book?