Around half the book is devoted to command line utilities: what they do, how to invoke them and the various options they take. Naturally, it is the options causing problems. While -c says to send stuff to the standard output in some utilities, in others it doesn't. For example it tells mke2fs to scan a device for bad blocks. It also covers boot issues, various shells, emacs, vi, sed, gawk and pattern matching. CVS and RCS for version control get good coverage. Gnome and KDE get a short chapter each and oddly, so does fvwm2. Some of these choices seem arbitrary. For Perl you are referred elsewhere, PHP isn't mentioned and neither is python.

In practice, the Linux man pages usually provide more information. Many of the book entries provide no more information than you would get from the usage instructions provided by the -h (or --help) option or by entering a nonsense option. The other complaint is inconsistency. Some of the commands have a usage example but most don't.

The problem with Linux In A Nutshell is that if you are actually at your desk using Linux, it is quicker to reference the system itself for the information but the book is rather too large to carry around to reference when you might need it (though why do you need it if you aren't using Linux at the time? Pub quizzes perhaps?).

Given that Linux commands comes with usage instructions, man pages and info pages as well as often having extra documentation, how-tos and source code--all for the versions you're using--it is hard to see quite what purpose its authors intended this book to serve. --Steve Patient

Jon Holman, Unix Review, Dec 2001
Linux in a Nutshell is one of my favorite books. I’ve
had a copy of it on my desk since the first edition was
released in 1997

See all Product Description