Slashdot Mirror
FreeBSD: The Complete Reference
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:
- FreeBSD Installation: Hardware requirements, installation instructions, and a general overview.
- Basic System Administration: Partitioning, startup procedure, file management, printer setup, user management, software installation, kernel configuration, and X.
- Network Configuration: Introduction to networking, dial-ups, client/server principles, basic firewalling.
- Servers: In-depth explanation of file, mail, web, and shell servers, plus an overview of DNS, NTP, DHCP, and other random services.
- 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.
- 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.
Why do I need a kernel? The new grub bootloader is actaully a operating system in it's own right!
Was the last line in the book:
"*BSD is dying."
It just seemed so out of place.
The post even said that it was 'official'.
Oh man, with all this contradiction, I'm going to have to stop believing things I read on the Internet... even Slashdot.
lysergically yours
Thank you, this will come in handy if it gets slashdotted.
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.
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.
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.
is BSD dying?
more like from the compleat-misspellings dept. ;)
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?
Thank you for pointing out the joke, your post will come in handy if I ever lose all sense of humor.
Indeed, what is the point of hardcopy computer books? I suppose a hard copy instruction manual would come in handy when installing or trouble
shooting, But so many books come without html
entirely. Computers are so much better at searching and hyperlinking than paper is, there's really no excuse for not providing hypertext. And there's really only one reason it's not done more, it would be copied.
Give me Classic Slashdot or give me death!
Can't they never get anything right ?
The book title is: FreeBSD: The complete necromancer's compendium
From the alt.comp.lang.learn.c-c++ faq:
> more like from the compleat-misspellings dept. ;)
Actually, "compleat" for "complete" in the titles of guidebooks is an ancient and revered practice, going back to this book.
I guess you learn something every day, huh?
Sentimentality is merely the Bank Holiday of cynicism.
- Oscar Wilde
I think this happens when you are awarded moderator points...
I am TheRaven on Soylent News
the obituary?
between the greater and lesser infinities sleep the dreams undreamt
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
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_
[Note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]
When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.
Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.
FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.
It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.
So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.
Discussion
I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.
From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.
There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.
Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.
Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?
Shouts
To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.
To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It's w
For the author not to know about vipw and not to mention vinum is rather lame IMHO. That's just too bad, because I love FreeBSD.
grisha.org
"...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?
> Indeed, what is the point of hardcopy computer
> books?
The ability to read them away from a computer and useful indexes (which no electronic book I have seen has -- they all rely on the generally poor searchability of the text).
FreeBSD is great.
FreeBSD is not great if you don't have a braudband connection though!
This is great! FreeBSD could use more books to counter the perception that tons of crappy leenucks books equates to high quality, when in fact, leenucks is such a low-quality waste of time, it's no wonder all the leenucks distros are dying by the droves.
First off: This Is Not A Troll!
Never having used any *BSD and only having a passing knowledge of Linux in its various flavors, where might one learn about the differences (dare I say Pros & Cons?) of FreeBSD and a Linux distribution? Maybe this is an Ask Slashdot question (I couldn't find a previous one, and a quick Google turned up only performance comparisons, not feature comparisons)
FPs must be content-free!
You forgot Tiger Penis Soup and Jawa racial slurs.
BT
For the true BSD afficionado, you'll be able to have your name sandblasted on to it and use it as a tombstone.
:)
With cool geek (oxymoron?) epitaphs like "Kill -9 JohnDoe"
First consider that there are a lot of commercial systems out there today - old systems that have lived for eons and eons - that currently use BSD.
Next consider that these old systems use old compilers because they haven't been updated in ages.
Finally consider that lowly users don't usually have access rights to upgrade such systems.
Given these three facts, it would seem that there is a need for cross-compilers from Linux and Windows (via cygwin or mingw, perhaps) to BSD, so that we can actually use these systems effectively. However, I have yet to find one good (i.e. that works) piece of information on the subject. Perhaps this isn't addressed in the book...but it is certainly an area to be addressed in SOME book about BSD.
Mod me down and I will become more powerful than you can possibly imagine!
Someday everyone will have fast connections. That isn't today.
Infuriate left and right
It hurts 'n' stuff.
ABCDEFGHIJKLMNOPQRSTUVWXYZ
,./;'[]!#$%^&*()_+?:"{}|\
Can I have my royalty check now, please?abcdefghijklmnopqrstuvwxyz
1234567890
I also like how we've both been modded down -1 Troll.
/. probably won't do much, posting it in a place where anyone and everyone active in FreeBSD development can read it, and give it a fair piece of thought might have some positive effects. You may need to tone down the angst a small bit though, mostly just to get people to actually process what you're saying first, instead of jumping to a knee-jerk flame. It'll take some careful articulation, but it appears you are capable of this (just a bit miffed, understandibly) :o)
I wasn't trolling, and neither were you.
Although posting your views and ideas on
I'm not a developer, but a user of Debian and FreeBSD, and I would really hate to see one of my two favourite OS's fade away.
Codewise, i think FBSD is a great BSD fork and a perfect balance between the spartanness of NetBSD and the retentative nature of OpenBSD.
All in all, i think the 3 major *BSDs have really got something valid and good, and i don't want to see any of them die.
Especially over politics. Nothing should go down like that.
-phaeton
The first thing I want to know when anybody talks about BSD is this: why precisely should I learn yet another OS? What do I get that I don't already get from Linux or Windows or QNX or Inferno or... I'm not suggesting that nobody needs to know BSD. But any review of a BSD book -- and the ensuing discussion -- should touch on the question of who should be interested in the topic.
Enough about Herb Schildt.
The review is painfully padded. All JSG seems to have to say is, "Looked for factual errors, couldn't find any. Liked the book, even though I disagreed with some of the advice." Throwing in a lengthy outline and a lot of useless trivia (imaginary domain names, forsooth!) to bring it up to a proper length is just lame.
Linking to Barnes & Noble's web site hurts your credibility. I assume people do it because they give better referral rates than Amazon, and/or you're pissed about Jeff's patent hunger. Well, forget it -- I don't want to deal with B&N's cruddy web site, abysmal customer service, and absurd inventory problems.
Bookpool.com has this book for $30.95. (Hint: search for 'FreeBSD'). It's $49.99 at bn.com. Do the math.
what is that smell? It's like something died in here..
Oh, it's the rotting corpse of BSD, being fed on by the maggots.
An excellent FreeBSD book is Michael Lucas' Absolute BSD. His Absolute OpenBSD book arrives soon.
Enjoy,
Helevius
Including obituary!
Now, is it dead at last?
Less is more !
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'm actually running FreeBSD on a production system already. Not a mission critical box I admit, but it's still a production system.
I know FreeBSD 5.0 is not rated for this sort of use, but I really wanted to try out SMPng and UFS2. Can't give any benchmarks, but my subjective opinion is that the dual PIII 400 wipes the floor with the single PIII 800 box it replaced.
I had a couple of niggles, but nothing major - no show-stoppers. Of them niggles, most have been solved by a cvsup and make kernel, followed by a reboot.
So as long as you have half a clue (i.e. you know which errors you can safely ignore) I'd certainly recommend 5.0 for all but the most crucial applications.
Do you mind, your karma has just run over my dogma.
I also googled for it but didn't find anything. I think you're right. The "facts" sounded impressive and authoritative but he just invented them to get karma.
For those looking for kickstart their collection, here are the FreeBSD books I own:
Absolute BSD: The Ultimate Guide to FreeBSD
by Michael Lucas
ISBN: 1886411743
FreeBSD: The Complete Reference
by Roderick W. Smith
ISBN: 0072224096
The Complete FreeBSD, Fourth Edition
by Greg Lehey
ISBN: 0596005164
FreeBSD Unleashed (2nd Edition)
by Brian Tiemann, Michael Urban
ISBN: 0672324563
I'd like to see a *real* "ask slashdot" of all the differences, too. Of course it might de-evolve into a flamefest, but I'd still like to see the attempt made.
Rednat isn't Linux.
You're an idiot.
*BSD is dying because, the only people who use it are idiots like you.
It doesn't sound too good that The Complete Reference comes with a one-CD FreeBSD distribution. That isn't enough space to fit many apps on. You can buy the FreeBSD Handbook in a boxed set with a big old stack of CDs, containg loads of apps.
Find free books.
The record is clear on one thing: no operating system has ever come back from the grave. Efforts to resuscitate *BSD are one step away from spiritualists wishing to communicate with the dead. As the situation grows more desperate for the adherents of this doomed OS, the sorrow takes hold. An unremitting gloom hangs like a death shroud over a once hopeful *BSD community. The hope is gone; a mournful nostalgia has settled in. Now is the end time for *BSD.
I thought it read, FreeLSD. And hashpot. Dopers rule.
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a mere fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
Those who can *BSD, those that cant Linux.
- Linux is for the clueless -
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS hobbyists, dabblers, and dilettantes. *BSD continues to decay, and nothing short of a miracle could save it at this point in time; for all practical purposes, *BSD is dead.