Slashdot Mirror

honestpuck writes "The Missing Manual series has been around for quite some time, but I have never felt the need to buy one until I started doing some serious work with iPhoto. iPhoto 2: The Missing Manual was a good volume to assist." Read on for the rest of honestpuck's review. iPhoto 2: The Missing Manual author David Pogue, Derrick Story, Joseph Schorr pages 336 publisher O'Reilly/Pogue Press rating 8 reviewer Tony Williams ISBN 0596005067 summary An good guide to iPhoto2 for beginner to intermediate users

One of the things I like about Apple's iApps is that they hide a great deal of complexity behind a simple interface; they do indeed make the complex simple. The drawback to this is that I often find myself ignoring the more powerful aspects of the application and never using it to its full. It was here that the Missing Manual came to my help.

The target audience for this book would probably be a little less technical than myself or the average Slashdot reader, however when I find myself in a field I don't understand well I don't mind a little stuff for the absolute newbie. This book has an entire first section that deals with photography and digital photography in particular that may be a total repeat for some, I found it a welcome reminder of how to get a good photograph along with some extremely useful hints about the new technology and choosing a camera. It covers such topics as composition and lighting for a host of different situations such as landscapes, night, portraits, children and sports.

It then goes on to a section of similar size on the basics that covers getting the photos from your camera to the Mac, organising the photos using albums and keywords and then editing your shots.

A third section covers the various ways of publishing and showing your photos such as printing, CD, and web pages, and a final section with some tricks and tips on things like managing your libraries. There are two appendices: one very useful troubleshooting guide, and a menu-by-menu look at iPhoto 2.

I particularly appreciated the thorough treatment of how to get the most out of iPhoto when printing photo books and creating web pages in the third section; it was here that I really discovered how little I knew from just 'playing' with the application. The book is peppered with useful information and tips that take you beyond the level that most of us discovered when we ran and used the program. The authors have also provided some marvelous explanations of what is going on, the "why" as well as the "what."

The book is well written with a readable, light, almost witty style that somehow deceives the reader as to the depth of the material being covered. It is only when I reflected back on how much the book taught me that I realised how well it had done the job.

O'Reilly have their usual web page for the book with a sample chapter, Table of Contents and Index. Pogue Press have a neat idea - they have a page that features all the software mentioned in the book. A neat idea that I liked a lot.

In conclusion, I would recommend this book to everyone who is serious about digital photography on their Mac. If you have used iPhoto for a long time you may think the book a waste, but I'd be surprised if even long-time users didn't get their money's worth out of this book. I much preferred the style of this volume to IDG's iPhoto 2 for Dummies , the only other real competitor for this volume was iPhoto 2 for Mac OS X: A Visual Quickstart Guide , and that is a shorter volume with less depth and less advice for photography and nothing on the camera technology, though I think Engst's writing seems a bit clearer at times.

I wouldn't buy a "Missing Manual" for every iApp or the operating system, but if you take the slogan for the series seriously, "The book that should have been in the box" (for the box is entirely devoid of books), I think they are a marvelous help for becoming a true 'power user.'

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

honestpuck writes "The Missing Manual series has been around for quite some time, but I have never felt the need to buy one until I started doing some serious work with iPhoto. iPhoto 2: The Missing Manual was a good volume to assist." Read on for the rest of honestpuck's review. iPhoto 2: The Missing Manual author David Pogue, Derrick Story, Joseph Schorr pages 336 publisher O'Reilly/Pogue Press rating 8 reviewer Tony Williams ISBN 0596005067 summary An good guide to iPhoto2 for beginner to intermediate users

One of the things I like about Apple's iApps is that they hide a great deal of complexity behind a simple interface; they do indeed make the complex simple. The drawback to this is that I often find myself ignoring the more powerful aspects of the application and never using it to its full. It was here that the Missing Manual came to my help.

The target audience for this book would probably be a little less technical than myself or the average Slashdot reader, however when I find myself in a field I don't understand well I don't mind a little stuff for the absolute newbie. This book has an entire first section that deals with photography and digital photography in particular that may be a total repeat for some, I found it a welcome reminder of how to get a good photograph along with some extremely useful hints about the new technology and choosing a camera. It covers such topics as composition and lighting for a host of different situations such as landscapes, night, portraits, children and sports.

It then goes on to a section of similar size on the basics that covers getting the photos from your camera to the Mac, organising the photos using albums and keywords and then editing your shots.

A third section covers the various ways of publishing and showing your photos such as printing, CD, and web pages, and a final section with some tricks and tips on things like managing your libraries. There are two appendices: one very useful troubleshooting guide, and a menu-by-menu look at iPhoto 2.

I particularly appreciated the thorough treatment of how to get the most out of iPhoto when printing photo books and creating web pages in the third section; it was here that I really discovered how little I knew from just 'playing' with the application. The book is peppered with useful information and tips that take you beyond the level that most of us discovered when we ran and used the program. The authors have also provided some marvelous explanations of what is going on, the "why" as well as the "what."

The book is well written with a readable, light, almost witty style that somehow deceives the reader as to the depth of the material being covered. It is only when I reflected back on how much the book taught me that I realised how well it had done the job.

O'Reilly have their usual web page for the book with a sample chapter, Table of Contents and Index. Pogue Press have a neat idea - they have a page that features all the software mentioned in the book. A neat idea that I liked a lot.

In conclusion, I would recommend this book to everyone who is serious about digital photography on their Mac. If you have used iPhoto for a long time you may think the book a waste, but I'd be surprised if even long-time users didn't get their money's worth out of this book. I much preferred the style of this volume to IDG's iPhoto 2 for Dummies , the only other real competitor for this volume was iPhoto 2 for Mac OS X: A Visual Quickstart Guide , and that is a shorter volume with less depth and less advice for photography and nothing on the camera technology, though I think Engst's writing seems a bit clearer at times.

I wouldn't buy a "Missing Manual" for every iApp or the operating system, but if you take the slogan for the series seriously, "The book that should have been in the box" (for the box is entirely devoid of books), I think they are a marvelous help for becoming a true 'power user.'

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

honestpuck writes "Linguistics has long been an interest of mine, and one of my fields of study, and I've recently read two good books that combine linguistics with other topics. The Keys of Egypt is the tale of history's most famous decoding task, the translation of Egyptian hieroglyphics and In The Beginning is the story of the King James Bible, the history, theology, politics, linguistics and technology that surrounded Bible translation and printing in Renaissance Europe and England." Read on for his combination review of two books that might inspire your curiosity, no matter how far from the usual Slashdot fare. In The Beginning & The Keys of Egypt author Alister E. McGrath & Lesley Adkins & Roy Adkins pages 352 & 368 publisher Anchor & Perennial rating 7 reviewer Tony Williams ISBN 0385722168, 0060953497 summary A good book on the history of the King James Bible & A decent read on the translation of hieroglyphics

Hieroglyphs The Keys Of Egypt was written by husband-and-wife archaeological team Lesley and Roy Adkins. It is subtitled "The Race to Crack the Hieroglyph Code," and starts with a short chapter that introduces the eventual winner of that race, the Frenchman Jean-Francois Champollion, and mentions his most serious rival, the Englishman Thomas Young.

The book goes on to examine Napoleon's expedition to Egypt which both brought the Rosetta Stone to light and started a period of French and European fascination with ancient Egypt. These were the two catalysts for the riddle's eventual solution.

This is a well-written book that looks at the struggle and race for translation and the political and academic machinations (often both combined) that surrounded Champollion. It is essentially a biography of Champollion, who grew up and worked amid the turmoil of the Napoleonic era. The story is a compelling one and the authors have done well to make it at times fascinating.

As a genre I find that 'scientific biographies' tend to be a little overblown and flowery, the writing not quite precise -- and Keys suffers from these shortcomings. I also felt that while the book is subtitled "The Race to Crack the Hieroglyph Code" it really only focuses on Champollion, while he is the eventual winner a little more effort in examining the others involved in the effort would have improved the book.

The Bible It can be argued that the King James Bible has had as large an effect on our language today as the work of Shakespeare. 'In The Beginning' has at its core the story of biblical translation, a topic you may think anything but fascinating. McGrath has done a good job in making this a compelling book.

He starts, as one may expect, with the story of Gutenberg and his first printed bibles. Before arriving at the King James he covers Martin Luther, the rise of Protestantism in Europe, Henry the Eighth, more than one hanging, and several other bible translations and translators. Along the way he manages to dispel a few myths I had held about biblical translation and the King James in particular. I always thought that it was the King James version that introduced the idea of the main body in roman type and words inserted to clarify meaning in italics, but it was actually an earlier English translation known as the Geneva Bible that first implemented this idea. After explaining the technology, theology, politics and linguistics nuances that led King James to permit (but not fund) a new translation, McGrath tells us how the translation was accomplished organizationally before examining some of the nuances of the translation itself. Some of the language in the King James was archaic even when it was published; translators had been instructed to lift from previous translations all the way back to the partial translation of William Tynsdale published 90 years earlier, and this at a time when the English language was going through the huge changes of the Elizabethan era. McGrath examines this aspect, pointing out such things as changes in verb endings and personal pronouns.

I found the book patchy. McGrath does a much better job covering the story up until the translation. It is harder to get a feel for how the translation was accomplished and how the various teams worked, and when he comes to examine some of the nuances of the translation, the text makes much harder going. If this had not been a part of the topic that interested me a great deal, I may have lost interest.

Conclusion

Both books may have their flaws but both are well worth the read. It is important to realise the history of science and language that have brought us to our current place and both these volumes do a good job of illuminating the past efforts of men who worked under entirely different pressures than we find today.

You can purchase both In The Beginning and The Keys of Egypt from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

honestpuck writes "Linguistics has long been an interest of mine, and one of my fields of study, and I've recently read two good books that combine linguistics with other topics. The Keys of Egypt is the tale of history's most famous decoding task, the translation of Egyptian hieroglyphics and In The Beginning is the story of the King James Bible, the history, theology, politics, linguistics and technology that surrounded Bible translation and printing in Renaissance Europe and England." Read on for his combination review of two books that might inspire your curiosity, no matter how far from the usual Slashdot fare. In The Beginning & The Keys of Egypt author Alister E. McGrath & Lesley Adkins & Roy Adkins pages 352 & 368 publisher Anchor & Perennial rating 7 reviewer Tony Williams ISBN 0385722168, 0060953497 summary A good book on the history of the King James Bible & A decent read on the translation of hieroglyphics

Hieroglyphs The Keys Of Egypt was written by husband-and-wife archaeological team Lesley and Roy Adkins. It is subtitled "The Race to Crack the Hieroglyph Code," and starts with a short chapter that introduces the eventual winner of that race, the Frenchman Jean-Francois Champollion, and mentions his most serious rival, the Englishman Thomas Young.

The book goes on to examine Napoleon's expedition to Egypt which both brought the Rosetta Stone to light and started a period of French and European fascination with ancient Egypt. These were the two catalysts for the riddle's eventual solution.

This is a well-written book that looks at the struggle and race for translation and the political and academic machinations (often both combined) that surrounded Champollion. It is essentially a biography of Champollion, who grew up and worked amid the turmoil of the Napoleonic era. The story is a compelling one and the authors have done well to make it at times fascinating.

As a genre I find that 'scientific biographies' tend to be a little overblown and flowery, the writing not quite precise -- and Keys suffers from these shortcomings. I also felt that while the book is subtitled "The Race to Crack the Hieroglyph Code" it really only focuses on Champollion, while he is the eventual winner a little more effort in examining the others involved in the effort would have improved the book.

The Bible It can be argued that the King James Bible has had as large an effect on our language today as the work of Shakespeare. 'In The Beginning' has at its core the story of biblical translation, a topic you may think anything but fascinating. McGrath has done a good job in making this a compelling book.

He starts, as one may expect, with the story of Gutenberg and his first printed bibles. Before arriving at the King James he covers Martin Luther, the rise of Protestantism in Europe, Henry the Eighth, more than one hanging, and several other bible translations and translators. Along the way he manages to dispel a few myths I had held about biblical translation and the King James in particular. I always thought that it was the King James version that introduced the idea of the main body in roman type and words inserted to clarify meaning in italics, but it was actually an earlier English translation known as the Geneva Bible that first implemented this idea. After explaining the technology, theology, politics and linguistics nuances that led King James to permit (but not fund) a new translation, McGrath tells us how the translation was accomplished organizationally before examining some of the nuances of the translation itself. Some of the language in the King James was archaic even when it was published; translators had been instructed to lift from previous translations all the way back to the partial translation of William Tynsdale published 90 years earlier, and this at a time when the English language was going through the huge changes of the Elizabethan era. McGrath examines this aspect, pointing out such things as changes in verb endings and personal pronouns.

I found the book patchy. McGrath does a much better job covering the story up until the translation. It is harder to get a feel for how the translation was accomplished and how the various teams worked, and when he comes to examine some of the nuances of the translation, the text makes much harder going. If this had not been a part of the topic that interested me a great deal, I may have lost interest.

Conclusion

Both books may have their flaws but both are well worth the read. It is important to realise the history of science and language that have brought us to our current place and both these volumes do a good job of illuminating the past efforts of men who worked under entirely different pressures than we find today.

You can purchase both In The Beginning and The Keys of Egypt from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

objectboy writes with a review of Chris Fehily's SQL: Visual QuickStart Guide, writing "This book teaches ANSI SQL-92 programming to database beginners and intermediates. The publisher, Peachpit Press, publishes mostly end-user and novice titles that usually go unnoticed by professional programmers. Its Perl and PHP books, for example, are of little practical or tutorial use to an experienced developer. In fact, I noticed this SQL book only because a junior developer was using it for a course. The book's table of contents, index, and a sample chapter are posted on Amazon.com. The book's official web site contains errata and other information." Objectboy's review continues below. SQL: Visual QuickStart Guide author Chris Fehily pages 424 publisher Peachpit Press rating 9/10 reviewer objectboy ISBN 0321118030 summary A lucid SQL tutorial and professional reference

What this book does right: The myth that it's more important for a programming book to be technically accurate than well written endures even though the opposite situation is true: A lucid explanation of a difficult concept or clever algorithm is more valuable than a bug-free implementation of same.

Consider Ken Henderson's The Guru's Guide to Transact-SQL , a book full of useful examples but so marred by the author's bloated style and disrespect for the language that I cringe every time I'm forced to read the text rather than simply lift a code snippet. Henderson even goes so far as to include an introductory section, titled "On Formality," about how he is going to split infinitives (even though their syntax is a burden for the brain to parse) and how he is going to use "data" in the singular sense (even though doing so can cause confusion) and how he considers "record," "row", and "tuple" to be interchangeable terms (even though they're not) and on and on. Readers would be aghast to find such self-exculpatory nonsense in the pages of Donald Knuth or Patrick Henry Winston. As for SQL: Visual QuickStart Guide, the author, a statistical programmer, presents each topic with a mathematician's sense of restraint and order. I've found few typos, no technical errors, and consistent use of technical terms.

Almost every aspect of SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER, and DROP is covered. What distinguishes this book is that every ANSI SQL statement -- and there are hundreds of examples -- was tested on six separate DBMSes: Microsoft Access 2002, Microsoft SQL Server 2000, MySQL 4.0, PostgreSQL 7.1, Oracle 8i, and Oracle 9i (8i and 9i differ considerably in SQL-92 compliance). The examples in each section increase in depth and complexity, so you can stop reading once you've learned what you need to know. When an ANSI SQL statement doesn't work as-is on a particular DBMS, the author shows you how to fix it or offers workarounds (which is particularly useful for MySQL, whose adherence to the SQL standard is poor). These DBMS-specific fixes are given as separate "DBMS Tips" apart from the main body of text, so they don't interfere with the conceptual flow. This organization is especially useful for consultants who have difficulty keeping track of how each implementation deviates from the ANSI standard, and is superior to the alphabetical, segregated approach of O'Reilly's SQL in a Nutshell.

This book was shoehorned into the publisher's Visual QuickStart format, which, as I implied earlier, doesn't work well for procedural languages, but does work for a declarative language like SQL. A two-column layout separates examples from explanatory text. Red type highlights the relevant portions of code and results. The book is extensively cross-referenced and has an 18-page index. This layout also makes the book a good quick reference for experienced programmers. Almost all the examples use a single, sample database (so there's no need to memorize multiple schemas). The code listings and sample database are available for download.

The derivative nature of programming books makes it difficult to determine whether the author truly has mastered the material. Writing a book is a difficult task (perhaps even harder than programming) but, at the risk of exaggerating my point, I suspect that any determined, organized, and competent programmer could write any O'Reilly Nutshell book by paraphrasing existing materials. But if an author establishes his credentials early, the reader gains a sense of trust that remains throughout the entire book. In the introduction to this book, the author avoids an error that almost every other SQL-book author commits: that SQL stands for structured query language. According to ANSI (the only legitimate arbiter here), it stands for S-Q-L and nothing more. Fehily even offers an amusing explanation of why structured query language is the worst possible description of SQL. Throughout the book, the author also scatters bits of practical advice (job candidates are wise to say my-es-kyu-el, not my-sequel), beginner-friendly insights ("Although SELECT is powerful, it's not dangerous: You can't use it add, change, or delete data or database objects."), and advanced topics (optimization, concurrency control, logical data independence). It is these asides and respect for basic research, rather than swaths of expository text, that lend authority.

This book describes the effects of nulls in almost every aspect of SQL, including the interpretation of null-contaminated query results. You can no more be a competent SQL programmer without understanding nulls than you can be a competent LISP programmer without understanding recursion. Particularly useful are the discussion of three-value logic (true/false/unknown) and an algebraic derivation of how a null can cause a subquery to return an empty result unexpectedly (which has bitten me more than once).

As a wizened developer weary of hand-holding users and junior programmers through routine queries, I've found it mollifying to give away copies of this book (it's cheap) to reduce my interrupt stack.

What's Missing: Some missing items that I would have found useful:

• A glossary
• A quick syntax reference
• A chapter about statistics
• A chapter about advanced SQL "tricks"
• DB2 coverage
• Coverage of security commands (GRANT/REVOKE)
• An expanded query-optimization discussion
• Improved normalization examples
• A little more mathematical rigor in the set-theory discussion

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

objectboy writes with a review of Chris Fehily's SQL: Visual QuickStart Guide, writing "This book teaches ANSI SQL-92 programming to database beginners and intermediates. The publisher, Peachpit Press, publishes mostly end-user and novice titles that usually go unnoticed by professional programmers. Its Perl and PHP books, for example, are of little practical or tutorial use to an experienced developer. In fact, I noticed this SQL book only because a junior developer was using it for a course. The book's table of contents, index, and a sample chapter are posted on Amazon.com. The book's official web site contains errata and other information." Objectboy's review continues below. SQL: Visual QuickStart Guide author Chris Fehily pages 424 publisher Peachpit Press rating 9/10 reviewer objectboy ISBN 0321118030 summary A lucid SQL tutorial and professional reference

What this book does right: The myth that it's more important for a programming book to be technically accurate than well written endures even though the opposite situation is true: A lucid explanation of a difficult concept or clever algorithm is more valuable than a bug-free implementation of same.

Consider Ken Henderson's The Guru's Guide to Transact-SQL , a book full of useful examples but so marred by the author's bloated style and disrespect for the language that I cringe every time I'm forced to read the text rather than simply lift a code snippet. Henderson even goes so far as to include an introductory section, titled "On Formality," about how he is going to split infinitives (even though their syntax is a burden for the brain to parse) and how he is going to use "data" in the singular sense (even though doing so can cause confusion) and how he considers "record," "row", and "tuple" to be interchangeable terms (even though they're not) and on and on. Readers would be aghast to find such self-exculpatory nonsense in the pages of Donald Knuth or Patrick Henry Winston. As for SQL: Visual QuickStart Guide, the author, a statistical programmer, presents each topic with a mathematician's sense of restraint and order. I've found few typos, no technical errors, and consistent use of technical terms.

Almost every aspect of SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER, and DROP is covered. What distinguishes this book is that every ANSI SQL statement -- and there are hundreds of examples -- was tested on six separate DBMSes: Microsoft Access 2002, Microsoft SQL Server 2000, MySQL 4.0, PostgreSQL 7.1, Oracle 8i, and Oracle 9i (8i and 9i differ considerably in SQL-92 compliance). The examples in each section increase in depth and complexity, so you can stop reading once you've learned what you need to know. When an ANSI SQL statement doesn't work as-is on a particular DBMS, the author shows you how to fix it or offers workarounds (which is particularly useful for MySQL, whose adherence to the SQL standard is poor). These DBMS-specific fixes are given as separate "DBMS Tips" apart from the main body of text, so they don't interfere with the conceptual flow. This organization is especially useful for consultants who have difficulty keeping track of how each implementation deviates from the ANSI standard, and is superior to the alphabetical, segregated approach of O'Reilly's SQL in a Nutshell.

This book was shoehorned into the publisher's Visual QuickStart format, which, as I implied earlier, doesn't work well for procedural languages, but does work for a declarative language like SQL. A two-column layout separates examples from explanatory text. Red type highlights the relevant portions of code and results. The book is extensively cross-referenced and has an 18-page index. This layout also makes the book a good quick reference for experienced programmers. Almost all the examples use a single, sample database (so there's no need to memorize multiple schemas). The code listings and sample database are available for download.

The derivative nature of programming books makes it difficult to determine whether the author truly has mastered the material. Writing a book is a difficult task (perhaps even harder than programming) but, at the risk of exaggerating my point, I suspect that any determined, organized, and competent programmer could write any O'Reilly Nutshell book by paraphrasing existing materials. But if an author establishes his credentials early, the reader gains a sense of trust that remains throughout the entire book. In the introduction to this book, the author avoids an error that almost every other SQL-book author commits: that SQL stands for structured query language. According to ANSI (the only legitimate arbiter here), it stands for S-Q-L and nothing more. Fehily even offers an amusing explanation of why structured query language is the worst possible description of SQL. Throughout the book, the author also scatters bits of practical advice (job candidates are wise to say my-es-kyu-el, not my-sequel), beginner-friendly insights ("Although SELECT is powerful, it's not dangerous: You can't use it add, change, or delete data or database objects."), and advanced topics (optimization, concurrency control, logical data independence). It is these asides and respect for basic research, rather than swaths of expository text, that lend authority.

This book describes the effects of nulls in almost every aspect of SQL, including the interpretation of null-contaminated query results. You can no more be a competent SQL programmer without understanding nulls than you can be a competent LISP programmer without understanding recursion. Particularly useful are the discussion of three-value logic (true/false/unknown) and an algebraic derivation of how a null can cause a subquery to return an empty result unexpectedly (which has bitten me more than once).

As a wizened developer weary of hand-holding users and junior programmers through routine queries, I've found it mollifying to give away copies of this book (it's cheap) to reduce my interrupt stack.

What's Missing: Some missing items that I would have found useful:

• A glossary
• A quick syntax reference
• A chapter about statistics
• A chapter about advanced SQL "tricks"
• DB2 coverage
• Coverage of security commands (GRANT/REVOKE)
• An expanded query-optimization discussion
• Improved normalization examples
• A little more mathematical rigor in the set-theory discussion

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

ctrimble writes "A bunch of folks on the pragprog Yahoo! Group have banded together to design and implement a 'pragmatic' programming language. Ostensibly, the language is informed by the principles in Hunt and Thomas's well-received book, The Pragmatic Programmer: From Journeyman to Master but the purpose of the language is to help ease some of the pain of development and bridge the impedance mismatch between the academic aspects of a programming language and the discipline of software engineering. The design is still very much in flux. If you're a programmer, this might be a language you'll be using in a few years (or earlier). This is your chance to get in on the ground floor. What kind of features do you want the language to have? What are your PL pain points? Where could this language do better than existing languages?"

Spencerian writes with a review combining two things you might not expect in one volume: the "For Dummies" label and Sun Solaris. (Raise your hand if you've never, ever looked through a "For Dummies" book.) Read on for Spencerian's summary of Solaris 9 For Dummies, which he says is a good book for the Solaris newbies, but not for everyone. Solaris 9 For Dummies author Dave Taylor pages 354 publisher Wiley Publishing rating 8 reviewer Kevin Spencer ISBN 0764539698 summary A" ...For Dummies" book like Solaris 9 For Dummies will never make you popular with other geeks. However, if you are a Solaris admin, perhaps giving this book to your users might stop them from asking you the same questions over and over.

I'm pretty intimate with the ...For Dummies book formula. I worked at the company a few years ago. The ownership of the book series has changed a bit, as has its cover art, but the basic setup remains.

Solaris 9 For Dummies is, as with many ...For Dummies books, a starter guide and reference. This isn't a book for administrators, and says so. Solaris 9 For Dummies maintains the book series' reputation as strong general references for users who are thrust (sometimes unwillingly) into new or different technology and need the basics in getting around, fast.

Author Dave Taylor is no stranger to UNIX, having written several notable UNIX beginner, intermediate and advanced references on UNIX in general, including books on Red Hat Linux, Solaris, and Mac OS X. Solaris 9 For Dummies works for SPARC hardware as well as Intel-based hardware. More about Dave Taylor's work can be found at his web site, Intuitive.com.

The ...For Dummies series books are pure references. They aren't meant to be read from cover to cover, which gives the author an advantage by writing topics and chapters without a lot of preamble. The information is just shallow enough to understand but never trivial, giving readers typically only what they require. The typical cross-references and tips are available to guide you along. Chapters delve into topics you expect from discussing a UNIX such as Solaris, such as moving about the new GNOME interface (which will replace the old CDE interface over time), running the basic applications and utilities, and the like. In the traditional format of these books, Solaris 9 For Dummies comes with a tear-out cheat sheet. This cheat sheet gives readers a basic CDE and GNOME interface menu command tree to make it easily to find, say, the Empty Trash command.

The book's topics include details on:

• File management
• Making a decent password
• Shells
• Text editors
• Using Writer and StarOffice
• Internet, Web, and Mail access
• Essential system administration

The author knows that UNIX isn't UNIX without a certain level of geekspeak, and so provides readers with a well-crafted introduction in the use of command lines and how they can be a Good Thing when using Solaris often for particular tasks. Many UNIX writers (especially developers) wrongly assume that anyone who uses a UNIX knows where and how to find or do what most might consider a routine task. In a ...For Dummies book, this thinking is not allowed, so the author adds enough background for you to get the gist, guides you on the essentials, and provides information that points you to find more complex answers elsewhere.

Solaris 9 For Dummies will not make your whites brighter, increase your personal intimate pleasure, or bring peace to the Middle East, and it's certainly not flashy. It's just a good book for the Solaris newbies, plain and simple. If you hack your kernel just for pleasure (gotta shave your palms regularly, I'm sure), you can be reasonably guaranteed this isn't the book for you. However, if you are an Solaris administrator and get plagued with user questions about basic tasks, maybe you should have your boss buy a few copies of Solaris 9 For Dummies for your users so you can continue your Quake3 fragfest uninterrupted.

You can purchase Solaris 9 For Dummies from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

honestpuck writes " I am a big fan of the written word on dead trees, but sometimes I like to have the written word where I can easily search it, or cut and paste from it. That's why I like PHP.net and why I decided to get a copy of O'Reilly's Web Programming CD Bookshelf. And I am pleased with it, though not ecstatic." Read on to see what honestpuck liked about this collection, and what drawbacks it may have for you. The Web Programming CD Bookshelf author [Various] pages 540 paper, 1189 HTML publisher O'Reilly rating 7 reviewer Tony Williams ISBN 0596005105 summary A good resource for PHP developers, overpriced for others

The Good The Web Programming CD Bookshelf (WPCB) consists of a CD and a paper copy of Webmaster in a Nutshell, 3rd Edition. The CD contains an HTML version of that, as well as Dynamic HTML: The Definitive Reference, 2nd Edition, Programming PHP, PHP Cookbook, JavaScript: The Definitive Guide, 4th Edition and Web Database Applications with PHP & MySQL. There is an excellent combined index of the six volumes and a nice Java search engine, QuestAgent Pro version 4.0.9. from JObjects. According to the documentation for the engine on the CD, "It has problems running with Mozilla 0.9 and 1.0 and Netscape 7 on Mac OS 9, and occasionally on Linux"; I had no problems running it on Mac OS X in Mozilla 1.3, Safari or Internet Explorer apart from a small visual problem with another tab in Mozilla (separate windows was fine, only another tab in the same window caused a problem).

All the contents pages and indices of the volumes are of course hyperlinked. Once you are on the pages of a 'book' the top of each page has a link to the contents page, next page, previous page and the search form. The bottom of each page has next and previous buttons (with the relevant page titles), a link to the books contents page and index and below them all a row of links to the Bookshelf home and each of the books. Taken together this makes moving through the books and finding the information you want easy, for the most part.

Once you start using the collection there are some great benefits. The ability to just cut and paste the example code right out of the text you are reading cannot be underestimated.

The books themselves are the quality you expect from O'Reilly - well-written, well-edited and containing the information you need on a given subject. The one you get on paper, Webmaster in a Nutshell is a good overview of HTML, CSS, XML, JavaScript, CGI and Perl, PHP and Apache that I find a good desktop reference. The others provide a good depth and perspective on their respective subjects.

The Bad

Obviously a great deal of the work of converting the books to HTML must be done by automated software, and sometimes you wish a little more had hand-work had been done. For example, Dynamic HTML: The Definitive Reference has an alphabetical list of all HTML and XHTML tags and their attributes -- as one page of 23,000 lines of HTML. The only way into this mammoth list is via the book index, there is no quick list of tags with links on a separate page or other fast way.

My other complaint about that content is that the selection of books is PHP heavy. If you are involved in using PHP to build websites this volume would be a great help; others may feel they would have been better served by a collection that dropped at least one of the PHP books in favour of, perhaps, The Perl Cookbook. Webmaster in a Nutshell is not as useful in this collection as you might think, some of what it contains is covered by other volumes in the set. That's not to say that it isn't an excellent book and a good choice as the one that comes in paper with the CD, just that once again I'm not sure it really needed to be in the collection.

That brings me to my final complaint, cost. Sure, 6 books for $130 U.S. seems like a bargain, but unless you are interested in all 6 books (which means principally developing for the web in PHP) it starts to be less of a bargain. If you think of it as more expensive than a six-month subscription to O'Reilly's online book service, Safari (which allows you ten books, changeable when you want) then this is less than a bargain.

Conclusion

If you are developing for PHP then this might be a good resource at a fair price; you'll find it almost indispensable and (unlike Safari) you can use it when you're offline. If you develop in some other environment, it is an overpriced way of getting a few books as electronic text. If you develop for the web in Perl, then have a serious look at The Perl CD Bookshelf instead, or perhaps consider a Safari subscription.

You can purchase The Web Programming CD Bookshelf from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

hmobius writes "In a world where developers are baying for customers' attentions, very few people can claim to command that of the developer. Their blogs may be the only clue to the higher level of thinking that they operate at, creating the answers to why and when code works in addition to the perennial how. Whether he likes it or not, Don Box is one such system-meister. He may dislike writing books, but when one comes out, people pay attention and read. His first foray into text, Essential COM, was the book to explain how COM worked, and his latest, Essential .NET, takes the .NET Framework's Common Language Runtime (CLR), and does exactly the same." Read on for the rest of hmobius' review. Essential .NET, Volume One author Don Box with Chris Sells pages 400 publisher Addison Wesley rating 8/10 reviewer Dan Maharry ISBN 0201734117 summary Great in-depth look at the CLR, but not for developers aiming to better their skills.

After chapter one's history of the evolution from COM to the CLR, the book takes a bottom-up approach to the CLR, starting with a deep and detailed six chapter look into the core elements of the platform. Chapter two begins with assemblies, the programmatic units in the CLR, and the implications of their construction. We learn how they are versioned, loaded and built, and why therefore they may be written in as many .NET languages as required. There's real depth to the material here -- you really do touch the bottom of the abyss, so to speak -- but it's countered with occasional levity that keeps this a readable book instead of a dense reference manual. The same is true of all the text. To wit, there's even some irony; "To allow old dogs to avoid learning new tricks, there is finalization," he declares in the next section on the Common Type System.

It's here that we discover how different types and interfaces are distinguished from themselves and from one another, and how their variations and relationships are kept separate by the CLR. It's refreshing to note that the proverbial big picture is never very far away from the commentary. After taking time to explore the avenues for types and interfaces, Box notes that types themselves aren't very interesting until you start working with instances of those types, and we're off again working through another thirty pages on how object instances preserve a sense of identity, how they are cast into other types and how they incorporate themselves into the concepts of reflection and metadata. Only then do we look at the actual lifecycle of an object, its creation, modification and disposal. The attention to detail is great, and there's little ambiguity in the text, but with that comes a slowness to this section that may leave readers frustrated.

One recurring theme of the book is the idea that while there is a very proper way and set of rules for doing things, there will always be circumstances in application development which call for exceptions to be made to those rules and made possible by .NET. This is true at a small scale and, as chapters six and seven prove, at a large one too, covering as they do how the CLR calls and runs methods first on a single machine and then over a wire. How does the runtime treat methods called explicitly, implicitly through a delegate, asynchronously, or as a combination of the three? How do remote calls and types bridge whatever gaps they must cross and activate the remote objects and methods they're targeting? The answers are here.

Essential .NET reflects Box's pride in .NET and also his slight dissatisfaction with it. You can sense that while he knows .NET version 1 is an improvement over COM, it's not as good as it could be and things are still be done in v2 and beyond. Chapter eight's look at AppDomains and in particular its discourse on threading within and through AppDomains is a good example of this. Meanwhile, we finally come full circle in our investigation of the CLR, seeing how the assemblies we built in Chapter 2 are resolved and executed within AppDomains. Exceptions to rules being included, we also see how objects references are marshaled across AppDomains for inter-application communication if this is required.

The last two chapters look at wider topics around the CLR in as much detail as they can for topics which have entire books dedicated to just them. Chapter nine covers code-access security and chapter ten topics which are not of the CLR but which be can be addressed from within a .NET application: explicit memory management, using p/invoke to import COM methods from DLLs and so on. Both are concisely written and to the point, but unsurprisingly leave you feeling like there's more to these topics than is covered here. Chapter nine is a great and clear introduction to code-level security, for example, but you'll get a lot more out of Michael Howard's book, Writing Secure Code if you want to know more.

Essential .NET isn't an easy read but everyone should try to read it at least once. Focusing on the CLR itself and how it deals with the components of an application means that it truly is aimed at the community of .NET developers as a whole (including those building and using alternate implementations of the CLR). The provided code examples are expressed in C#, but this is incidental, really, and won't stop VB.NET, J# or any other developers getting a great deal out of this book.

This is a dense, complex volume that requires a fair amount of effort to understand and use, and to some extent this may put people off. On the other hand, it is so packed with great nuggets of information that they may be inspired to keep reading. Of course, there is the question of whether this book will actually improve your .NET development skills, but in riposte, you can honestly say that no volume details the CLR and its potential so well, and that this alone is worth the book's cover price.

You can purchase Essential .NET, Volume One from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

More Sci-Fi reading for your summer weekend: Javed Ikbal writes "Decipher by Stel Pavlou is a mind-blowing work of science fiction. If you thought Stephenson's Snowcrash did a great job of bringing myth and science together, bite into this. I am still shaking my head over the amount of research that must have gone into this book." Read on for Javed's review. Warning -- spoilers within. Decipher author Stel Pavlou pages 422 publisher St. Martin's Press rating 10 reviewer Javed Ikbal ISBN 0312280750 summary Ties together all the myths you can think of (Atlantis/Pyramids/Maya/Inca/Noah/Flood) and does it very well.

What it's about: Tag line: Mankind had 12,000 years to decipher the message. We have one week left ...

Let me make something clear. Although this is my first Slashdot review, I do not give this book a 10 lightly.

March 2012. The whole world is experiencing unusual weather. A commercial research ship is drilling in Antarctica when the drill breaks against something hard. The pressure sends up chunks of C-60 (Fullerene) with glyphs on them. Cameras show a wall miles under Antarctica: Atlantis has been found.

A linguist, a geologist, a physicist and an engineer convene at CERN, invited by the U.S. military to analyze the C-60 and the writing on it. They discover that the mysterious molecules can create standing waves to temporarily solidify liquids. The government wants them to go on an expedition to the site, assisted by some U.S. marines.

In the meantime, the earth is being hit by gravity waves emanating from the sun, and astronomers predict massive solar flare activity that will practically destroy earth.

And home by dinner time ... Natural disasters are occurring everywhere because of the solar activity, and a plasma cloud is being sucked into a hole in Antarctica. Atlantis is sucking in all that energy without any trouble. Everyone is hoping that the answer to the coming cataclysm lies in Atlantis. Just to round things up, the Vatican wants Atlantis blown up with an atomic bomb, and the U.S. president agrees. The marines will be carrying a warhead; if Atlantis does not yield its secret, it will be blown away.

The linguist and the physicist figure out that every 12,000 years the sun goes through a massive coronal mass ejection (it's a pulsar, but with a 12,000 year period) and last time this happened Atlantis was destroyed. They were building equipment to prevent the destruction, but could not do it on time. However, the Atlanteans left automated nanobots to complete the task for the next time it happened. The time is now.

The expedition reaches the core of Atlantis, but the nanobots, as a result of over 12,000 years of artificial intelligence evolution, do not want to help humanity. They know that if humanity dies, they will take over; but if humanity survives they will have to go. Last-minute tension, the hero gives his life for humanity, the earth is turned solid for a second by standing waves generated from structures all over the earth, the gravity wave passes safely and then earth and all its creatures are returned to normal form. All is well.

I strongly recommend this book, but note that this is not a quick read: you have to assimilate this book to appreciate the wide scope. Good reading!

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

JayBonci writes "It may come as a surprise that within the pages of 'Perl 6 Essentials' lies what could be two books, despite its length. If not for lack of cover space, it could easily bear the names "Perl6 for Perl5 programmers" and "Parrot in a Nutshell". Both topics are concise and clearly covered, despite their relatively different audience." Read on for the rest of Jay's review. Perl 6 Essentials author Allison Randal, Dan Sugalski, and Leopold Totsch pages 208 publisher O'Reilly rating 9 reviewer Jay Bonci ISBN 0596004990 summary A solid look ahead at Perl 6, and a reference for Parrot developers

Make no mistake, Perl 6 isn't here yet, but it's coming. The book starts with a good explanation of "the plan"; chapters 1-3 deal with the history, goals, and design considerations of the project. It's a good conceptual overview of the process about how it has been run so far, and how it seems to be continuing. Chapter 3 is of special interest, as it showcases some of the in-depth thought that has been poured into the project. Though we all aren't language theorists, it helps allay some of the fears that change brings while being completely fascinating reading.

This first part of the book isn't very useful without a fairly solid Perl 5 background. It wastes no time in chapter 4 discussing syntactical differences in the v5 to v6 transition. Programmers should be pleased with the practicality of the approach to the new language, as it refers to the new structures and features, and how they solve simple workarounds that Perl veterans are used to in Perl 5. Currying, multimethods, class definitions and structures, new operator syntax, and the dynamics of the new regular expression engine (now called rules) are all touched on, and their values made obvious to the reader.

The last three chapters are for those interested in Parrot development and those who wish to port languages to Parrot. (There are active projects to port Python, Ruby, and even .NET to Parrot.) The section has a slight perl slant to it, but is really about the interpreter and compiling / running Parrot code. It is a fairly complete reference to the different parts of PASM (Parrot Assembly Language), and its role in porting languages to use Parrot. A comfort with assembly language basics is assumed in these sections, as the syntax and concepts of registers and machine code are made easier with general assembler familiarity. This part was somewhat dry for me, as it reads more like a reference than anything else, but it covers the topic fully without droning or leaving anything out. Examples are abundant and range from the simple, to the integrated, and are enough to get people started programming and writing tests with Parrot bytecode.

It should be noted that this book is valid and accurate now, but any development project can make changes quickly. There are places where the authors have admitted that a feature isn't in stone, and is possible to change. According to chromatic, an editor for O'Reilly, the plan is to update the book once a year until Perl 6 is released. Until then, a great place to keep up to date for the casual observer is at the p6p digest. This book goes down a lot easier than the Apocalypses, RFCs, and Exegeses, and I'd heavily suggest it to anyone who is serious about being ready for 6 or joining in on development . I preordered it from Amazon when I saw it was coming out, and am quite happy with my investment.

Table of Contents

1. Project Overview
   • The Birth of Perl 6
   • In the Beginning . . .
   • The Continuing Mission
2. Project Development
   • Language Development
   • Parrot Development
3. Design Philosophy
   • Linguistic and Cognitive Considerations
   • Architectural Considerations
4. Syntax
   • Variables
   • Operators
   • Control Structures
   • Subroutines
   • Classes and Objects
   • Grammars and Rules
5. Parrot Internals
   • Core Design Principles
   • Parrot's Architecture
   • The Interpreter
   • I/O, Events, Signals, and Threads
   • Objects
   • Advanced Features
   • Conclusion
6. Parrot Assembly Language
   • Getting Started
   • Basics
   • Working with PMCs
   • Flow Control
   • Stacks and Register Frames
   • Lexicals and Globals
   • Subroutines
   • Writing Tests
   • PASM Quick Reference
7. The Intermediate Code Compiler
   • Getting Started
   • Basics
   • Flow Control
   • Subroutines
   • IMCC Command-Line Options
   • IMCC Quick Reference

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

Jeff Carroll writes "Developers building Java applications for wireless handheld devices have been looking forward for some time now to the release of devices supporting version 2.0 of the Connected Limited Device Configuration (CLDC), and version 1.1 of the Mobile Information Device Profile (MIDP). These new releases contain support for features demanded by developers that didn't make the original releases. In support of CLDC 2.0 and MIDP 1.1, Roger Riggs and his team of authors from Sun, Nokia, and Motorola have released Programming Wireless Devices with the Java 2 Platform, Micro Edition, Second Edition (since I don't have a copy of the first edition, I can only evaluate the new edition on its own merits)." (Read on for his review.) Update: 07/23 16:31 GMT by T : Whoops -- that's CLDC 1.1 and MIDP 2.0, not the other way around. Programming Wireless Devices with the Java 2 Platform, Micro Edition, 2ed. author Roger Riggs, Antero Taivalsaari, Jim Van Peursem, Jyri Huopaniemi, Mark Patel, Aleksi Uotila pages 464 publisher Addison-Wesley Professional rating 7 reviewer Jeff Carroll ISBN 0321197984 summary In-depth introduction to and reference on CLDC 2.0 and MIDP 1.1.

As is characteristic of the titles I've seen from Sun's Java series, this book goes into great detail about architectural decisions, standards process, and philosophy underlying the new release. The first six chapters are given over to this discussion. This material is mostly great for experienced developers seeking a deeper understanding, occasionally so abstract as to be silly (as in the case of the Java washing machine and its downloadable stain-removing code), but likely to be of only secondary interest to new J2ME developers focused on coming up to speed.

What this book does best is comprehensive exposition of the J2ME APIs. There are chapters dedicated to the APIs for forms, graphics, games, sound, persistence, and networking, with code samples offered in most cases, and a Java Almanac-style reference to all J2ME-specific classes and interfaces is provided as an appendix. Features that are new to the J2ME second edition are clearly identified.

The remainder of the book constitutes a detailed discussion of the new technologies for event-driven launch, application security, and over-the-air deployment, perhaps the most potentially confusing of which is event-driven application launch. While the book explains the new technology well, it doesn't address how it will be introduced by network operators, or how it might interact with or replace similar existing proprietary technologies such as Sprint's MUGlets.

Another subject that is not dealt with here that will soon be relevant to developers for any particular J2ME-supporting network is that of optional packages (OPs) - features to be supported at the option of particular device vendors and/or network service providers. It is fairly clear that, going forward, the wireless network infrastructure and its supported features will be an integral part of the J2ME platform that will have to be taken into account by developers, and books which fail to discuss popular and commonly adopted OPs will be of limited usefulness (you'd think that Sun would know that after all that rhetoric about the network being the computer). In general, a book of this sort would benefit from the participation of network operators, as it does from that of device manufacturers Nokia and Motorola.

All the code samples and background on architecture notwithstanding, this book is clearly targeted at experienced Java programmers, not handheld device programmers working in other technologies. If you don't already know Java, this book will not teach you. There is also nothing said here about selection, configuration, or use of development tools; readers who are not already adept at the use of J2ME development tools, including the Wireless Tool Kit (WTK), should not expect to acquire that knowledge from this book. (People who need help in this area may want to consider Jonathan Knudsen's Wireless Java or Kim Topley's J2ME in a Nutshell.)

Keeping the aforementioned caveats in mind, this is an excellent introduction to and reference on the new release of J2ME.

You can purchase Programming Wireless Devices with the Java 2 Platform, Micro Edition, 2ed. from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Charles McColm writes "As one of the flock of Linux desktop users I have always taken it for granted that Linux is inherently more secure than Microsoft Windows. The truth is, I've never really paid much attention to Linux security, even on the Linux router I had running for a year. I always knew I should be concerned about security, but I never found a good starting point until I decided to review O'Reilly's Linux Security Cookbook (LSC)." Read on below for Charles' review. Linux Security Cookbook author Daniel J. Barrett, Richard E. Silverman & Robert G. Byrnes pages 311 publisher O'Reilly rating 9/10 reviewer Charles McColm ISBN 0596003919 summary LSC covers a wide range of security issues from installing an intrusion detection system to detecting network intrusions.

As the title suggests, LSC is a series of different Linux security "recipes." I found the cookbook-style of presentation both good and bad. Some recipes were a breeze to follow (such as the gpg recipes). Other recipes I felt could have been ordered a little better. The ipchains/iptables recipes in Chapter 2 are terrific, but I had to wait until the 19th recipe in the chapter to find out how to make the ipchains/iptables recipes stick. Though it makes sense to have saving a firewall configuration near the end of the chapter, I would have put the information after the first few recipes.

The only chapter that I glossed over was Chapter, "4 Authentication Techniques and Infrastructures." Chapter 4 covers Linux-PAM, OpenSSL and Kerberos. The chapter begins with a recipe for creating a PAM-Aware Application. I started to type in the C code but stopped a few lines from the end, it just didn't make sense for me to have this knowledge at this time. The introduction at the beginning of Chapter 4 is very good, but on the whole it is one of those chapters I've slotted for future reference. OpenSSH is discussed at the beginning of Chapter 4 but covered in more detail (an entire chapter) in Chapter 6.

The chapters I found most useful were those on intrusion detection systems (Chapter 1) and GPG (Chapters 7 & 8). Actually, I found almost all of LSC useful except the previously noted Chapter 4. Some of the software covered in the recipes are programs I've never heard of before, John the Ripper for example. Other recipes cover those programs I know I should check out (like Snort) but have never taken the time to.

LSC is for the most part very easy to follow. The authors have been very careful to mention when software (snort for example) might or might not be included and how to find and install it. I got tripped up a little in the first chapter (which covers tripwire), because I tried downloading and compiling the tripwire source found at the tripwire web site. I obtained the source from a couple of recommended sites. In one instance tripwire failed to compile correctly, in another it compiled but kept segfaulting when I tried to initialize the database. It wasn't until after I emailed O'Reilly that I saw mention further in Chapter 1 that tripwire is included with Red Hat Linux. One of the authors, Daniel J. Barrett, also emailed me to tell me that it was on the third CD - doh! The upside of this little tale is that I got to know aide (another intrusion detection system) a little better after I installed it on my Debian-based notebook.

I happen to think that computer books are overpriced. I have bought a number of $50-$90 computer books that ended up being doorstops after about a month and useless after a couple of years. Because of this experience I am a bit more stingy when shelling out for a computer book. Though I hate reading online documentation (I wear glasses and cannot stare at text on the screen for a long time), I have forced myself to read a lot more online documentation over the past year. This is one instance where I would be willing to shell out the $61.95 Canadian for a book. The Linux Security Cookbook covers a wide range of potential security problems and it presents its solutions such that each takes only a few minutes to implement.

I've saved what is actually covered in LSC for the end of this review. My intention in this review has been mainly to present my experience with LSC so that other members who are also still desktop users, or have never really been concerned with Linux security issues can take away the fact that despite a few sticking points I found this book to be a great source for information on different Linux security issues. For those concerned with the meat of the book, here's how it breaks down:

1. System Snapshots with Tripwire
2. Firewalls with iptables and ipchains
3. Network Access Control (xinetd, inetd, preventing DOS attacks)
4. Authentication Techniques and Infrastructures (PAM, SSL, Kerberos)
5. Authorization Controls (su and sudo)
6. Protecting Outgoing Network Connections (OpenSSH)
7. Protecting Files (permissions, GPG)
8. Protecting Email (all popular mail user agents, SSL and SSH)
9. Testing and Monitoring (Jack the Ripper, Cracklib, Snort, tcpdump, syslog)

You really need to have a good look at the table of contents to get an idea of all this book covers. I have written about it from a desktop-user standpoint, but there are so many recipes that I couldn't cover everything. There are many great code snippets that more advanced users would find useful.

If you don't have an intrusion detection system, need to grant some of your users limited root privileges, have been using the default firewall rules (or don't have a clue about iptables/ipchains), haven't checked your system for root kits or insecure protocols, then the Linux Security Cookbook should be at the top of your reading list.

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

Simon P. Chappell writes "The Eclipse IDE has thundered into the collective consciousness of Java developers since its release by IBM as Open Source Software. Up until this time, the majority of available documentation at the Eclipse website has been for plug-in developers, with scant attention given to the rest of us that actually want to use the tool for anything else. This book restores the balance and brings much needed help to those interested in this IDE." Read on for the rest of Simon's review, about which he says "Full Disclosure: I received a free, review copy of this book, so feel free to assume that I've been bought off and have traded my technical integrity to put about an inch of dead tree on my shelf." Eclipse in Action author Gallardo, Burnette and McGovern pages 383 (15 page index) publisher Manning rating 8 reviewer Simon P. Chappell ISBN 1930110960 summary A good book that lives up to its name.

Overview With a book like this it's difficult to know where to pitch the level. Do you aim for the lowest common denominator or do you assume some experience on the part of your reader? This book seems to have pitched itself well, not pandering to the absolute Java newbie, not afraid to get down into the code and yet gentle enough that newer Java developers can follow easily. The heavyweight chapter on writing plug-ins is at the back where it shouldn't frighten those of a sensitive nature.

The book is divided into two sections. The first and largest section concerns actual use of Eclipse during Java application development. The second section is for those who wish to write plug-ins for Eclipse.

The book takes a very 'Test Driven Development' approach to Java development and this shows in the manner that Eclipse is presented and taught. Emphasis is given to the tools that come with Eclipse, especially Ant, Junit and the CVS client. For those already skilled in these tools, this might seem like filler, but remember that there are still pitifully few Java developers using even these simple and free tools. My hat is off to the authors for their TDD evangelism, skillfully disguised as Eclipse usage instruction.

What's To Like I liked the progression followed in the book, first teaching the basic operation of Eclipse and then moving on to the tools that come with the base install. What's To Consider Some may consider that the material on Ant, Junit and CVS is filler. The 'Test Driven Development' theme may be a little too much evangelism for some.

I use Eclipse on a Mac OS X box and I felt that there was very little discussion concerning the cross-platform attributes of the tool. All of the screenshots were from a Microsoft Windows build of the software; a Linux or OS X screenshot would have been helpful.

One more niggle and then I'm done. There is no information on using Eclipse with other programming languages (a couple of paragraphs in the introduction chapter doesn't really count). I've recently started tinkering with Ruby and have used a Ruby plug-in to allow me to work within Eclipse as I learn the language. This is a wonderful testament to the power and extensibility of Eclipse.

Summary This is a good book. You know it's a good book when you already use the tool (both pure Eclipse and IBM's WSAD) regularly and you find yourself learning things that you had not previously been aware of. If you are working with Java and want a good free IDE that's going to grow with you, then Eclipse is a tool you should try -- and consider this book the User's Guide that would have been in the box if Eclipse came shrink-wrapped.

Table Of Contents

1. Using Eclipse
2. 1. Overview
   2. Getting started with the Eclipse Workbench
   3. The Java development cycle: test, code, repeat
   4. Working with source code in eclipse
   5. Building with Ant
   6. Source control with CVS
   7. Web development tools
3. Extending Eclipse
4. 1. Introduction to Eclipse plug-ins
   2. Working with plug-ins in Eclipse

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

Craig Habeck writes "As a Dilbert aficionado, I was intrigued when a colleague handed me a book that he described as 'like Dilbert written from the point of view of the Pointy-Haired Boss.' I read it over the weekend and came into work on Monday with my sides still sore from laughing." Read on for the rest of what sounds like a good antidote to the plague of management/motivational airport books. The Management Secrets of T. John Dick author Augustus Gump pages 268 publisher Mainland Press rating 9 reviewer Craig Habeck ISBN 0970874693 summary Dilbert in Prose - Sort Of

In fact, the resemblance to Dilbert is confined to the setting (a dysfunctional company) and a general atmosphere of corporate absurdity that will be only too familiar to many of us. This is a novel which is closer in tone to British humor of the 1950s. For 268 pages we go inside the head of T. John Dick, a hopelessly incompetent but supremely self-confident marketing manager, transferred from Boston to a small company in the fictitious town of Falling Rock, North Carolina.

Dick immediately goes about licking the company into shape, with disastrous and frequently hilarious results.

The humor derives chiefly from the character of TJ himself and the stark contrast between his self-image and reality. In his mind, he is a dynamic leader in tune with the latest management techniques. He is fond of sharing with us some of his "greatest strengths," including his ability to see "the big picture." In reality, he is a bumbling nincompoop, obsessed with petty details like the tidiness of his employees' desks and his mind-numbingly complex Meeting Room Reservation Procedure, the constant flouting of which drives him to distraction. He is completely unaware of the source of amusement he provides for his colleagues, particularly his nemesis, the laconic VP of Finance, and Hans Kartoffel, the German acting President of the group.

TJ applies the same cutting edge management techniques to his marriage, with similar results. He is completely oblivious to his wife's frequent affairs. We would feel sorry for him, if he weren't such a jerk. In fact, we do occasionally find ourselves sympathizing with him, but we soon get over it.

TJ's unusual management style leads him into some unique (and very funny) situations. His arrangements for a celebration of two million accident-free work hours lead to a fire which burns down half the factory. He attempts to struggle through a violent attack of diarrhea during an important presentation. He accidentally locks the company's president in a restroom stall and endeavors to free him without being noticed. So accident-prone is he that we are hardly surprised when his golf pants catch fire. Of course, no matter what happens, TJ always has a perfectly rational explanation - and it's never his fault.

The character of TJ is an exaggerated but nonetheless very recognizable version of bosses we have known. I laughed, but I also squirmed at the thought that there is no shortage of TJs running around gumming up the gears of industry. The book will appeal to anyone, engineer, product manager, secretary or other corporate wage slave, who has ever had to deal with an incompetent boss or colleague.

The Management Secrets of T. John Dick concludes with a series of completely absurd topics for readers discussion groups. My favorite: "TJ's obsession with trivial details....might be described as a serious personality defect. Discuss some of your own personality defects. Bet you've got some real doozies! You might like to help your co-members by pointing out some of theirs."

The book's back cover reveals little about its author, Augustus Gump, so I turned to the publisher's web site www.mainlandpress.com. Gump has previously published a number of short stories and his humorous articles have appeared in the Charlotte Observer and other regional newspapers. This is his first novel. I will be looking out for his next one.

You (or your boss) can purchase The Management Secrets of T. John Dick from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Eater writes "With a 1.1 release imminent, this review may be of interest to users of Linux on the desktop. OpenOffice.org is a group of small projects that collectively make up the open source community's premier office suite. Based on code from Sun's StarOffice and maintained by a worldwide community of developers, the OpenOffice.org project provides a full-featured office application suite. It includes a language independent API and open XML-based file formats." Read on for the rest of Eater's review. OpenOffice.org Resource Kit author Solveig Haugland, Floyd Jones pages 1040 publisher Prentice-Hall PTR rating 9 reviewer Eater ISBN 0131407457 summary An essential introduction to OpenOffice.org.

With a stable 1.0 release and spectacular cross-platform functionality, it's finally time to seriously consider putting this software to work in your company. Whether you are completely new to OpenOffice.org or just moving from its predecessor StarOffice, you'll want to take a look at OpenOffice.org 1.0 Resource Kit from Prentice Hall PTR.

The "kit" consists of a well written tutorial book and a companion CD-ROM. The book's authors (Solveig Haughland and Floyd Jones) are salty veterans in the technical training field, and it shows in the quality of the text. The CD contains the OpenOffice.org release itself, as one might expect. It provides builds for every supported platform, to include the Mac OS X developer alpha version. At the time this review was written, two minor upgrades have been made available since my book's CD-ROM was pressed. These are, naturally, available for free via the OpenOffice.org web-site. In addition to the releases, the CD includes templates, macros, and examples from the developer community. The authors provide additional templates and resources at http://www.getopenoffice.org

The first five chapters of the book are devoted to basic issues such as installation, migrating existing data, printer issues, and global setup tips. Special guidance is given to users switching over from StarOffice, or even that Redmond company's office suite. Speaking of that company, OpenOffice.org is superb at converting Word, Excel, and PowerPoint files into its own open formats. The book shows how to use the handy "AutoPilot", which can perform batch conversions of your existing data for use with OpenOffice.org's equivalent applications. Originals are kept safely intact-- AutoPilot produces converted copies. This could make a large office transition much easier, if not completely seamless.

The next six chapters cover the creation of written documents in fantastic detail. The organization of this section is quite intuitive; you'll easily learn how to create a simple letter. When you're ready to write your memoirs, you won't need to buy another book--it's all there: complex formatting options, page layout functionality, object manipulation, linking cross-references, and indexing. And don't forget office goodies like mail merges, label printing, and business cards.

Chapters 13-17 focus entirely on web-page development. Serious web designers may find this section bordering on useless, but the casual user will be able to create a home page without learning a single tag of HTML.

The next several chapters deal with Calc (a spreadsheet program), Impress (for creating presentations), and Draw ("the best drawing program you've never used," say the authors). The layout of each section follows the comprehensive example from the earlier chapters detailing OpenOffice.org's word processor, Writer. Basic topics are organized neatly along with the more advanced ones, and neither seem to get in the way of the other. Both the novice and the expert will find very little lacking from this material.

Organizations who deal frequently with databases will not be disappointed with OpenOffice.org, either. The final three chapters of the book explain how to incorporate data from any flavor database you're likely to be using in your network. Throw in an appendix on macros, and you've got one very complete tutorial masquerading as an all-in-one reference. I'm very picky when it comes to my geek shelf space, and this one gets high marks in all the important areas: comprehensive, well organized, and with a great signal-to-noise ratio.

We have learned that superior open source software alone isn't always enough to supplant the existing closed source way of doing things. However, "document it, and they will come!" The OpenOffice.org 1.0 Resource Kit will go a long way toward fulfilling that prophecy.

Reader Marcus Green sent in a review of this book as well. Here are some of his thoughts:

In addition to the document management features the book covers the more "Page Layout" style features of StarOffice such as the ability to manage columns and to place vertical text running up the page. These are features I was not even aware existed in StarOffice before I read this book.

The StarOffice companion has over 1030 pages, but it is really bigger than it sounds because it is very dense. Although it has many screen shots, plenty of use is made of text based instructions. Instead of repeating instructions, the text will often point you to the page where a concept was first explained. This does break up the flow of instructions but it also means that the book contains more information than if they had repeated the text every time it was needed.

I found the section on the graphics module useful because I had not realised how StarOffice has some slightly non-standard ways of working with menus and selections. For example I spent quite a bit of time trying to get the 3d shapes menu to pop out and show all the possible shape options. It was only on a closer reading of the text of this book did I appreciate that you need to click and hold down the mouse for a few seconds before the menu pops out.

The tone of the book comes across as being created by people who like the program rather than a creation of a faceless corporation. Thus in the graphics section they have included the amusing Moose with moving fly graphic that is used for the logo of the JavaRanch website. Here is an example of the text style from the section on macros. "Macros can do things like open a file when you do a particular task, process data, or take your grandmothers' credit cards and buy $3000 worth of cat toys." It also features a section titled "Turning Off Annoying Features," which of course is about the autoformatting and word completion.

You can purchase the OpenOffice.org Resource Kit from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

honestpuck writes "Earlier this year I decided to learn Java. I'd spent some time using JavaScript without really getting my hands too dirty but I'd pushed it way to far and realized I needed a bigger hammer. Grabbing a copy of Learning Java, 2nd Edition from O'Reilly I started learning. First problem, I have to admit I've stayed away from object-oriented programming; after all, I've been writing software for nigh on twenty years without it - why make life hard? Sure, I understood the concepts and I'd done a little but never in a language so strongly committed to OO as Java." Read on for honestpuck's review of Head First Java, which he compares in style and content to Learning Java. Head First Java author Bert Bates, Kathy sierra pages 650 publisher O'Reilly rating 8 reviewer Tony Williams ISBN 0596004656 summary Good, offbeat Java tutorial with new approach to learning computer topics

The Good

Of course, you can't learn Java without a good understanding of object-oriented languages. I made fairly heavy going with 'Learning Java' until I decided to dive in head first. Head First Java, that is -- a new book from O'Reilly that has a totally different attitude to teaching than I've seen before in computer books. It also looks like this might be the start of a series from O'Reilly, the website an introduction seem to assume that there will be more 'Head First' titles and I hope so. The style is humorous, full of graphics, cartoons, puzzles, quizzes and crosswords. It reminds me of the textbooks that used to try and teach me geometry and algebra in high school or my daughter's elementary books on Roman and Greek history I purchased for her at the British Museum. The style didn't work to teach me much algebra and geometry, but I wasn't anywhere near as motivated. This time, it worked. In a couple of weeks I worked through the book and finally have Java skills where I can branch off and start coding the projects I had in mind (though something more advanced will be required soon.)

In the introduction the authors examine learning and explain why they designed the book as they did. To quote from one section: "Some of the Head First learning principles. Make it visual. Put the words within or near the graphics. Use a conversational and personalized style. Get the learner to think more deeply. Get -- and keep -- the reader's attention. Touch their emotions." They argue that our brain is tuned to novelty, and that their style provides the novelty to keep your brain turned on. They also provide ten tips for good learning. That's one thing that seems to set this book apart from most other computer books, they say they think of their reader as a learner and indeed that's the way you are treated by the book. You can start to get a feel for their ideas by visiting headfirst.oreilly.com, a site devoted to the series. You can also grab a couple of example chapters from the books web page, which also has the usual marketing info, table of contents and errata.

The Bad

When compared to Learning Java the coverage is not as good. Head First really only covers the basics, up to and including creating a GUI with SWING and then touches a number of others; Learning Java goes on to explore, with a fair depth, network programming, web programming, servlets, applets, Java Beans, XML and other topics that are only touched on briefly in Head First. If the style of learning does not suit you then this will be an incredibly irritating and useless book, I'd give it a try first, though. If it isn't for you then the style of Learning Java might be better.

Conclusion

When you get down to it, though, the only way to really decide on the worth of a tutorial is to decide how well it teaches. Head First Java excels at teaching. OK, I thought it was silly, I had a hard time making myself do the exercises, fill out the crosswords and solve the puzzles. Then I realized that I was thoroughly learning the topics as I went through the book. Learning Java was doing the same job, but the dry traditional method wasn't doing as well. Both books are well written, designed and constructed -- the style of Headfirst Java just made learning, well, easier.

It would seem to me that the 'Head First' approach is going to work wonderfully for the more 'beginner' topics, books for introducing you to a new style of programming, a new language or a radically different operating system or application. So if you're looking for a book to introduce you to Java then I can recommend Head First Java. Now if I could only find a book as good to introduce me to Common Lisp.

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

honestpuck writes "Earlier this year I decided to learn Java. I'd spent some time using JavaScript without really getting my hands too dirty but I'd pushed it way to far and realized I needed a bigger hammer. Grabbing a copy of Learning Java, 2nd Edition from O'Reilly I started learning. First problem, I have to admit I've stayed away from object-oriented programming; after all, I've been writing software for nigh on twenty years without it - why make life hard? Sure, I understood the concepts and I'd done a little but never in a language so strongly committed to OO as Java." Read on for honestpuck's review of Head First Java, which he compares in style and content to Learning Java. Head First Java author Bert Bates, Kathy sierra pages 650 publisher O'Reilly rating 8 reviewer Tony Williams ISBN 0596004656 summary Good, offbeat Java tutorial with new approach to learning computer topics

The Good

Of course, you can't learn Java without a good understanding of object-oriented languages. I made fairly heavy going with 'Learning Java' until I decided to dive in head first. Head First Java, that is -- a new book from O'Reilly that has a totally different attitude to teaching than I've seen before in computer books. It also looks like this might be the start of a series from O'Reilly, the website an introduction seem to assume that there will be more 'Head First' titles and I hope so. The style is humorous, full of graphics, cartoons, puzzles, quizzes and crosswords. It reminds me of the textbooks that used to try and teach me geometry and algebra in high school or my daughter's elementary books on Roman and Greek history I purchased for her at the British Museum. The style didn't work to teach me much algebra and geometry, but I wasn't anywhere near as motivated. This time, it worked. In a couple of weeks I worked through the book and finally have Java skills where I can branch off and start coding the projects I had in mind (though something more advanced will be required soon.)

In the introduction the authors examine learning and explain why they designed the book as they did. To quote from one section: "Some of the Head First learning principles. Make it visual. Put the words within or near the graphics. Use a conversational and personalized style. Get the learner to think more deeply. Get -- and keep -- the reader's attention. Touch their emotions." They argue that our brain is tuned to novelty, and that their style provides the novelty to keep your brain turned on. They also provide ten tips for good learning. That's one thing that seems to set this book apart from most other computer books, they say they think of their reader as a learner and indeed that's the way you are treated by the book. You can start to get a feel for their ideas by visiting headfirst.oreilly.com, a site devoted to the series. You can also grab a couple of example chapters from the books web page, which also has the usual marketing info, table of contents and errata.

The Bad

When compared to Learning Java the coverage is not as good. Head First really only covers the basics, up to and including creating a GUI with SWING and then touches a number of others; Learning Java goes on to explore, with a fair depth, network programming, web programming, servlets, applets, Java Beans, XML and other topics that are only touched on briefly in Head First. If the style of learning does not suit you then this will be an incredibly irritating and useless book, I'd give it a try first, though. If it isn't for you then the style of Learning Java might be better.

Conclusion

When you get down to it, though, the only way to really decide on the worth of a tutorial is to decide how well it teaches. Head First Java excels at teaching. OK, I thought it was silly, I had a hard time making myself do the exercises, fill out the crosswords and solve the puzzles. Then I realized that I was thoroughly learning the topics as I went through the book. Learning Java was doing the same job, but the dry traditional method wasn't doing as well. Both books are well written, designed and constructed -- the style of Headfirst Java just made learning, well, easier.

It would seem to me that the 'Head First' approach is going to work wonderfully for the more 'beginner' topics, books for introducing you to a new style of programming, a new language or a radically different operating system or application. So if you're looking for a book to introduce you to Java then I can recommend Head First Java. Now if I could only find a book as good to introduce me to Common Lisp.

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

livegoats writes "No self-respecting culture maven can deny their love affair with Napster. If you weren't spending your spare time in the years 99-00 downloading MP3s like a champ, it's likely you were still in diapers or dancing with wolves. Oh, Napster, we loved ye when. Joseph Menn's All The Rave: The Rise and Fall of Shawn Fanning's Napster carefully chronicles the life of the company -- from its age of innocence, though its battle with the powerful music industry, to its slow unraveling in 2001, a foreshadowing event for the rest of the dot-com world." Read on for Livegoats' review. All the Rave: The Rise and Fall of Shawn Fanning's Napster author Joseph Menn pages 368 publisher Crown Publishing Group rating 7 reviewer Libe Goad ISBN 0609610937 summary If you love to read about the dot-com bust -- over and over -- this meticulously researched tome is for you. Keep a drink handy, however, it gets dry in parts.

One thing's certain: Menn, who covered Silicon Valley for the Los Angeles Times, meticulously researched his subject. The book is loaded with facts and figures, but more impressive is the level of National Enquirer-worthy details Menn milked from mountains of transcripts and one-on-one interviews.

Menn's discoveries can be described as nothing less than shocking, at least for anyone who hasn't followed the story blow-by-blow. We learn about Shawn's money-grubbing uncle, John Fanning, whose shady business practices cost the company numerous investors, but also the respect of his own family. Menn writes that at first Shawn Fanning was pleased when his uncle drew up papers incorporating Napster, Inc. Then the elder Fanning told Shawn he would be getting only 30 percent of the company. John Fanning would keep the rest. Shawn was stunned.

Menn also exposes Napster executives' ignorance of copyright laws, the company's pay-off to rapper Chuck D so he would publicly support file sharing and rockstress Courtney Love's flirtations with Shawn, whom she once introduced at an award show as her future husband.

With a boatload of rock stars and other curious characters, you'd think the spectacle of it all would overshadow the book's business patois. Menn attempts, valiantly, to do so, but it's still evident that All the Rave is a long-handed exercise in business reporting rather than a drama-filled account. There is little surprise in the overarching Napster story because most readers will know how the story ends before cracking open the front cover.

If you're still committed to All the Rave, the best reading takes place in two separate sections: the first on the peer-to-peer program's incubation, and the second on Napster's attempt to take on the well-muscled music industry.

In Chapters 1 and 2, Menn introduces Shawn Fanning, an unassuming high school kid who comes from humble beginnings. Though his life doesn't exactly make for a Horatio Alger story, it's interesting to see how Shawn stops pursuing a sports scholarship for college and instead focuses on computer programming.

After his uncle John gives Shawn his first computer, the aw-shucks kid from Massachusetts comes across a brilliant idea, peer-to-peer file sharing, which he develops with the help of friends in several online communities. The story is touching, and it's fascinating to take a behind-the-scenes look at how the program originated, first through Shawn and then as the product of a tight-knit online community.

Techies of all stripes will be amused as Menn attempts to make computer programming jargon edible to the mainstream reader. Just imagine explaining terms like IRC and warez to your grandma, and you'll have a good idea of the language in these beginning chapters. Despite a few cornball explanations, however, it's still refreshing to see past Napster's media hype and to see Napster for what it started as: a labor of love created by a kid who wanted nothing more than to take advantage of the online universe.

Following chapters barrel through the company's beginnings, dedicating much space to vilifying John Fanning, who seems to deserve every bit of consternation the reading public can muster. After the shock of the elder Fanning's behavior wears off, however, you'll find yourself dragging through painfully detailed accounts of acquiring executive and meetings with skeptical venture capitalists. Anyone who isn't utilizing All the Rave as a handbook on how not to run a business can skip to Chapter 7, in which Menn shifts the book's focus to Napster's delicate dance with the music industry. It's a Davey and Goliath tale for the 21st century. To accent the vastness of the undertaking, Menn dishes out a brief history of the music biz, offering such a compelling analysis of the Napster/music industry camps that it could easily be expanded to fill an entirely different book.

If you don't want to read at all, you can simply look at the pretty pictures midway through the book. Talk about a yearbook: there are pictures of Shawn's hacker pals, a photo of a wilting Lars Ullrich from Metallica, Jack Valenti and other corporate clowns, smiling like there was something to be happy about.

And maybe there was. In the end, Menn shows how Napster was, like other dot-coms, "little more than a publicly supported pyramid scheme, built on the long-true presumption that an even dumber investor was just down the road."

If you want a solid study on copyright law and running a business, Menn's read will not disappoint. If you're looking for a fluffy piece of literature that will keep you awake into the wee hours, try the one with the bespectacled boy on the cover. You probably know the one I'm talking about -- Harry something or other...

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

Peter Wayner writes: "When I mentioned the Mad Scientist Club short stories to a co-worker, he rolled up his sleeve and showed me the burn scars on his arm. The books, he said, did this to him. Not literally, but by misguided inspiration. In one of the tales, the boys in the Club launch a fleet of fake flying saucers to frighten their hometown of Mamouth Falls. The scars came when the colleague tried to imitate the book, but used real gasoline to add a bit of zip to plastic cleaner bags turned UFOs. Now, that the rediscovered full-length novel about the Club, The Big Kerplop is being republished with a bit of a splash, some adults may look at stories like this and decided that there's a danger that kids might start imitating the novels. The bigger danger, though, may come if they don't." Read on for the rest of Peter's review. The Big Kerplop author Bertrand R. Brinley pages 217 publisher Purple House Press rating 9 reviewer Peter Wayner ISBN 1930900228 summary The Mad Scientists rediscovered, in greater depth -- fun reading for kids and adults.

This novel isn't really new, although it is for all practical purposes. The author, Bertrand Brinley, had much success with the collections of short stories about the seven boys who dreamed of being scientists one day. The short stories continued to stay in print and even seemed to inspire a hack Disney adaptation, but only rumors about The Big Kerplop circulated on the Internet. When the copies of The Big Kerplop would trade on Ebay, they often closed at prices in the hundreds of dollars. Free markets can't ignore messages like that and the Purple House Press purchased the rights and relaunched the books.

It's easy for a Slashdot reader to understand how the stories could command such affection. The boys in the stories live in the netherworld between capability and responsibility. (Enjoy it if you're still there.) They have ham radio sets, fishing boats, weather balloons, and plenty of other gadgets to put to use in tweaking the noses of their buffoonish elders and only a few chores to get in the way.

The books are set in the early 60's before Bhopal, Three Mile Island, and Agent Orange rained on the big Science parade. Brinley worked for Lockheed and Martin during one of the the most romantic periods in aviation history, save perhaps the early days of the Wright Brothers. The books are infused with a certainty that rational thought guided by the scientific method and salted with a bit of pluck and wit could solve any problem. I think everyone here can agree that the entire club would be open source coders today, although it's not clear if they would embrace the BSD or GPL license. It may not even be stretching things to say that groups who wrote and distributed DeCSS are working through the same themes as the Mad Scientist Club, albeit on a global scale.

The novel is prequel to the collection of short stories that tells the backstory of how the boys found each other and discovered how a firm devotion to scientific principles could be put to work showing up the grownups. As they say on Fark, hilarity ensued many times.

The earlier short stories took up only 20-30 pages apiece, but this novel stretches to more than 200 pages, making it an entirely different animal. The characters are better drawn, the scenes are set with more than a sentence or two, and the plot twists back upon itself a few times. It's a leisurely read that makes the earlier stories seem a bit cartoonish or slapstick. This sophistication is a pleasure for me to read at my technically grownup age, but it may be why the novel didn't gain the same traction as the short stories. The laughs are driven more by character and dialog than by the setting and action. The short stories are basically set pieces, but the novel is more of a study in character. That's good for anyone who grew up loving the books, but it may mean that the current crop of 8-12 year old boys should wait a year or two before diving in.

The length of the novel also gives Brinley more room to flesh out the adults and let them play more than rubes to the Mad Scientists' schemes. The town's politicians are still a bit overstuffed, but Colonel March, the commander of the local Air Force base, is hardly a foil or a nemisis. Constable Billy Dahr, though, is still around to be the goat.

I suppose I should say something about the story. The Club, or at least the early core of what would become the Club, is out fishing on Strawberry Lake when a fleet of B52s flies over. Something makes a big kerplop in the lake and the Club spends the rest of the book saving the day, defying their elders and deploying some cool gadgets and the scientific method. This is a deeper, richer and very satisfying return for the characters.

Some of these tricks could get you some scars I guess but that's not the worst future awaiting a young reader. First, chicks dig scars -- although that theorem lies well outside of the scope of this book. Second, this may be the adult in me, but kids today seem fatter, lazier, and more hogtied than ever before. Yes, these words will haunt me when my children get bigger, but I think that Brinley hits the sweet spot between obedience and irreverence. Forethought and care save the day in these books, not caprice and whim. The characters are neither insolent nor cowed by authority. The important thing to remember is that the scientific method celebrated by the books does not suggest replacing a few candles with a burning pie plate filled with gasoline. At least not without first doing a bit of research on the safest way to ensure all of the energy turns into hot air.

You can purchase The Big Kerplop from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page. Peter Wayner is the author of several dangerous and incendiary books like Disappearing Cryptography and Translucent Databases . Don't burn them without standing at a safe distance.

XenonOfArcticus writes "I first came upon Matt Ridley when Slashdot reviewed Genome: The Autobiography of a Species in 23 Parts (here and here ). Ridley's finely-honed technical writing style could make a treatise on the Boston White Pages intriguing and enlightening, and his treatment of the human Genome was simply eye-opening. I had to have more, and went out immediately to order every Ridley book I could find. Luckily, The Red Queen and The Origins of Virtue were already available and his latest, Nature via Nurture was just hitting shelves. Prepare yourself for my ongoing Overview of Ridley in Three Parts." Read on for the rest of Xenon's review. The Red Queen: Sex and the Evolution of Human Nature author Matt Ridley pages 405 publisher Penguin Books rating Excellent reviewer Chris 'Xenon' Hanson ISBN 0140245480 summary Why sex is the reason humans are at the top of the food chain.

After laying our souls (and chromosomes!) bare in Genome, Ridley swiftly moves on to a topic that is variously fascinating and taboo: Sex. Every Slashdot user it seems wants more information about it. Ridley immediately tackles the Paradox of Sex: In an asexual organism, every individual of the species can create offspring. In sexual creatures (like people!), only the female can produce young. What's so great about sex then, that overcomes this obvious numerical handicap? In eleven brisk chapters, Ridley unravels the riddles with examples of how and why other species Do It (or Don't It), and what it all means.

Topics explored (though not claimed to be definitively explained) include mitochondrial DNA, dowries, the genetic foundations of harems, how males of a species could develop flagrant 'handicaps' like bright coloration or songs, monogamy, polygamy, adultery and a small species of New Zealand snail that suffers from a parasite named (I'm not making this up) Microphallus. One of the most compelling concepts is that a species' strongest competitor (and driving force behind their evolution) is their own kind, not their foes. In the end it is this argument, called The Red Queen (after a Lewis Carrol character that runs quickly but never gets ahead) that explains so much of our evolutionary hodgepodge of DNA and instinctive behaviour.

Around the world The Red Queen hustles, dissecting the environmental clues given by the mating rituals and biology of various species, asexual, sexual, heterosexual, hermaphroditic and otherwise, comparing them to Homo Sapiens, "the sexiest primate alive" (except for bonobos). As for humans, Ridley divulges how walking upright and our large brains are connected to our comparatively slow maturation, long lifespan and lack of hair. Always in the background is the unquestionable tenet: No one is descended from a celibate organism.

Ridley daringly takes on feminism and gender equality by pointing out that males and females DO differ genetically (duh!) and that in other species the effect of this difference is quite marked. Rather than degenerating into a misogynistic orgy of gender-bashing, he exposes the reasons why (among other differences) men might actually be better at reading maps and women might be more social. Both genders have to get along in order to continue the species, so understanding our differences may be a boon to all. While in the mood for controversy, Ridley delves into the reasons for the genetic-confounding phenomena of homosexuality in a species.

You don't need to have read Genome to read Red Queen, but if you have, you might find all of the puzzles fitting together into an even bigger picture, to be further sketched out in The Origins of Virtue and Nature Via Nurture. This book is not illustrated and probably won't help you get a date next weekend, but it might explain why you're instinctively attracted to those three young blondes at the bar. And why they're all more interested in the cinderblock quarterback of the football team. And despite what my inbox tells me, it has nothing to do with the size of a certain part of your anatomy, but rather the size of ... well, go read the book.

Table of Contents

• Human Nature
• The Enigma
• The Power of Parasites
• Genetic Mutiny and Gender
• The Peacock's Tale
• Polygamy and the Nature of Men
• Monogamy and the Nature of Women
• Sexing the Mind
• The Uses of Beauty
• The Intellectual Chess Game
• The Self-Domesticated Ape

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

Grant Willey writes "Deploying a License-Free Wireless Wide Area Network? Want to learn the intricate details from an authoritative expert who has personally designed and installed hundreds of license-free outdoor broadband wireless networks? This book isn't just for WISPs (wireless Internet service providers), this book is for you!" Read on for Grant's review of Deploying License-Free Wireless Wide-Area Networks from Cisco Press. Deploying License-Free Wireless Wide-Area Networks author Jack Unger pages 352 publisher Cisco Press rating 8 reviewer Grant Willey ISBN 1587050692 summary This is an information packed publication designed to assist you with the planning, installation, and maintenance of wireless WAN's.

This information packed publication is designed to assist you with the planning, installation, and maintenance of wireless WANs. You'll receive help with many commonly faced deployment challenges including site surveying, antenna evaluation and selection, overcoming real-world obstacles, solving noise and interference problems, maximizing available bandwidth, and working safely with tower structures and wireless gear. And, if you're presently pursuing a wireless technology certification such as Planet3's CWNA, CWNI, CWSP, etc, this book isn't written as a study guide, but it does provide vitally important information to help you earn these respected certifications.

Whether you're an experienced LAN/WAN professional or are new to the field and looking to "get your feet wet," this book will enrich your knowledge and possibly open new doors of opportunity for you. Being an experienced LAN/WAN professional with 19 years of experience and dozens of certifications, I thank the author for not filling the book with dry-humored jokes, useless "real life" experiences, and confusing diagrams/ illustrations. This book is grammatically correct, technically accurate, focused, and very helpful whether you're pursuing wireless certification or not. Beginner and experienced networking professionals will appreciate the "vendor neutral" content of the book. The book is published by Cisco Press, but contains no specific references to CISCO brand hardware/software. I believe this makes the information even more useful to technicians and installers who work with varying vendor equipment. While many concepts and methodologies are the same, this book is true to its name and offers little help in the way of assisting you with indoor WLAN deployments. The wealth of useful information contained in Appendix B, "Wireless Hardware, Software, and Service Provider Organizations" is absolutely priceless and much appreciated.

Here's how the book is organized: Chapters 1 and 2 are an introduction to wireless WANs and explain wireless technology fundamentals. Chapters 3-5 dive into network architecture, conducting site surveys, and selecting appropriate antennae. Chapters 6-9 discuss actual equipment selection, installation, interference resolution, and the provision of broadband wireless Internet access. Chapter review questions are located at the end of each chapter and serve as a "pop quiz" to reinforce key concepts and technologies covered.

Comparing this book to others is relatively easy. I haven't found any other publications dedicated to the planning, installation, and maintenance of wireless WANs! While there are a plethora of theoretical RF and wireless technology books already in print, no single publication dedicates its content to explaining the technologies like this book does. In addition, I appreciate the author's strong emphasis on installation and technician safety -- an area not many authors seem to write about. This book will not bog you down in theoretical RF discussions, but rather allows you to learn through the introduction of real-life examples, explanations, and suggestions based on the author's actual installation experiences.

The book contains no CD-ROM or marketing material. Published in March 2003 (prior to the now finalized 802.11g standard), the book primarily covers 802.11a and 802.11b technologies. Both Mr. Unger and Cisco Press deserve a round of applause!

You can purchase Deploying License-Free Wireless Wide-Area Networks from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

dbc15 writes "A timely and much needed update to the first edition, Fwais 2.0 is an excellent overview of the current landscape and psychology involving intranet, vpn and Internet host security while correctly addressing the positives and negatives of firewall / internet security and the techniques used by hackers." Firewalls and Internet Security, Second Edition. author Cheswick-Bellovin-Rubin, 2003 pages 433 publisher Addison-Wesley rating AA++ reviewer D Bruce Curtis, Ceo, American Interconnect ISBN 020163466X summary Incorporating an Internet firewall from start to finish.

The authors start with hacking and security needs analysis, progress thru strategies and techniques, and end with useful security formulas, hypotheses and real life examples. They draw upon their own experiences and observations about network security and host protection to give the reader a well-rounded view of the concepts of security as they apply today. The book is well written with simple examples and antecedents. They have taken great care to explain how hackers work and their methodology. The best thing about the book is that it does not go into great detail about unnecessary finite security specifics and shows what works best while adding value by allowing the reader the opportunity to think for themselves and address their own needs. They maintain the premise that: " Simple security is better than complex security: it is easier to understand, verify, and maintain."(Page 81) while covering the types of attacks not only by method, but also by class, ranging from the kiddie script up to the sophisticated tunneling and VPN methods.

FWAIS 2.0 is a comprehensive guide to the most common security problems while not wasting time on the insignificant. It includes a good set of general rules and the tool sets necessary to secure a network at any level. FAWAIS 2.0 covers current protocols and allows simple guidelines for flexibility in determining your own network needs. It describes the weaknesses in both hardware and software while addressing their relational aspects in easy to understand terms. Written with Freebsd in mind many of the techniques in this edition adapt well to other sources such as Linux, Os/X, Unix, NetBsd, and Solaris.

The entire premise of the book revolves around the concept that old style layered security is not as good as it may appear. And that internet security and firewalls are a holistic endeavor of system integration and design. The authors have taken care to show just how difficult it can be to keep up with large network topology and lend truth to the fact that there is no such thing as absolute security.

The concepts found in this book cover subjects such as :

• What firewalls can and cannot do, capabilities and weaknesses.
• What filtering services work best.
• What services and practices are overkill.
• Why firewalls are necessary, the risks to servers and the servers relationship to proper firewall installation.
• What the steps to hacking are and the methodology used to break into a host.
• The why, what and where of limiting services and the tools to secure the appropriate functions.
• Types of firewalls and best practices for implementing security while building and designing firewalls.
• Why building your own firewalls may be your best solution.
• Applying past experiences to your firewall design.
• Intrusion detection systems and their role as a network tool in firewall construction.
• Honey pot examples showing how the techniques have been used to thwart and frustrate potential adversaries.

This is not a how to book written with step-by-step specific fill-in-the-blanks, connect-the-dots, detailed mechanical guidelines; it addresses the real needs of the administrator in relation to actual daily situations. As they state on page 213 "-we don't think the hard part of firewall administration is data entry, it is knowing what the appropriate policies are."

The second edition is well documented and includes plenty of good link references, appendices and bibliography resources to help any professional keep current with the ever-changing environment of network defense.

Any organization evaluating current security needs should find the second edition helpful for determining their security goals and a comprehensive guide to help design, implement and deploy firewalls. The second edition is a definite must for any security library, certification-training program or public/private classroom situation.

I recommend Firewalls and Internet Security as the best starting point for anyone who might be considering any changes in company security structure or earning their security certifications.

You can purchase the Firewalls and Internet Security, Second 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.

PotPieMan writes "I recently finished reading JSP and Tag Libraries for Web Development, a book for JSP developers wanting to improve their skillset. Read on for my review." It's not a new book, but still relevant. JSP and Tag Libraries for Web Development author Wellington L.S. da Silva pages 420, including appendices publisher New Riders rating 6 reviewer PotPieMan ISBN 0735710953 summary A guide to designing and implementing JSP applications, with a focus on tag libraries.

The Scoop Web developers and designers have long wrestled with strategies for combining their efforts. Web developers don't mind looking at code but dislike dealing with the look of a page, while Web designers are the opposite. Dynamic Web page technologies, such as Microsoft's ASP, Perl's many template systems and Web frameworks (Text::Template, HTML::Template, HTML::Mason, CGI::Application, etc.), and PHP, were designed to give both developers and designers a chance to do their work without stepping on each other's toes.

Sun's answer was to release the Servlet API and later extend that to make JavaServer Pages. Initially, there was no clear role separation for servlets and JSPs, since a servlet could generate and display HTML just as easily as a JSP could perform business logic. The Model 2 architecture, based on Smalltalk's Model-View-Controller (MVC) design pattern, showed that servlets and JSPs complemented each other. Tag libraries extended the functionality of JSPs in a way that made it easier for developers and designers to collaborate.

JSP and Tag Libraries for Web Development is mostly targeted at Web developers who want advice on designing JSP applications and incorporating tag libraries. The book covers custom tag libraries, the Jakarta Struts framework, and various commercial and noncommercial tag libraries, such as Jakarta Taglibs.

What's to Like? The author starts with an introduction to servlets and JSPs, including a decent explanation of MVC. If you are comfortable with servlets and JSPs, this discussion is really more of a review than anything else.

The next two chapters introduce tag libraries and the author's example application (a simple article and author tracking system). The author illustrates the lifecycle of a tag, which helps if you haven't really used or written custom tags before. Da Silva also gives a very detailed discussion of tag library descriptors (TLDs). Some details might have been better left as an appendix, but it is nice to see such a comprehensive explanation of what you can put in a TLD.

Da Silva then spends about 100 pages on writing simple tags, iteration tags, body tags, and making all of these types of tags cooperate. The discussion is again very detailed, but seems unfocused in many parts. Very little of the code in these chapters ties in with his example application.

Next, the author spends three chapters on the Jakarta Struts framework. He explains how Struts naturally fits into the MVC design pattern and gives various examples of how to structure your Struts application. He also includes an entire chapter on finishing his example application, going over Struts ActionForms, Struts Actions (including a method to prevent double submission that I had not seen before), and Struts' method of internationalization on JSPs.

Finally, the author runs through the Jakarta Taglibs project and some commercial tag libraries. Brief examples are provided, but this chapter really needed more attention than da Silva gave it.

What's to Consider Overall, JSP and Tag Libraries for Web Development feels unfocused. The author's central points are explained well in many places, but lost in many others. With some reorganization, I think the book could make a much stronger case for appropriate uses of tag libraries, both application-specific and general (e.g. Struts and Taglibs).

Sections where general tag libraries are discussed read very much like the documentation available on project Web sites, such as the struts-html tag library documentation. These really should have been left as an appendix, with better explanations and usage examples provided in their place.

I was also very disappointed in the author's use of Struts Action classes. He combined various actions (add, edit, delete, etc.) to perform on a specific object and tested for a URL parameter to decide what to do. In my opinion, each action should be encapsulated in one Action class (AddObjectAction, EditObjectAction, and DeleteObjectAction). The author's design leads to URL hackery which Struts tries to avoid.

Recently, Struts released a stable version of the 1.1 series, which this book does not cover (it was published in early 2002). Readers should be familiar with the Struts documentation for this release before picking up this book.

The book's Web site is under construction, and I've been able to find little information on the publisher's site.

The Summary A okay book with room for improvement. While the author shows his technical knowledge, the book loses its direction in places. Most developers can probably get by with the documentation available on the Web. Table of Contents

1. Understanding the Tag Library Extension API
2. 1. Introduction to Servlets and JavaServer Pages
   2. Introduction to Tag Libraries
   3. Writing Custom Tags
   4. Cooperating Tags and Validation
   5. Design Considerations
3. The Struts Framework
4. 1. The Jakarta Struts Project
   2. Struts Tag Libraries
   3. Anatomy of a Struts Application
5. The Jakarta Taglibs and Other Resources
   1. The Jakarta Taglibs Project
   2. Commercial Tag Libraries
   3. Other Resources
6. Appendices
7. 1. Tomcat
   2. Allaire JRun
   3. Orion
   4. MySQL
   5. Mapping Servlet-JSP Objects
   6. The Apache Software License, Version 1.1

You can purchase the JSP and Tag Libraries for Web Development from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Ursus Maximus writes "If you have read an introductory book or two about Python programming, but you are far from being an expert, then you will benefit a lot from reading this book. If you are a competent programmer in any other language, you will benefit from this book. If you are an expert Python programmer, you will also benefit from this book." Ursus Maximus's review continues below. Text Processing in Python author David Mertz pages 520 publisher Addison Wesley rating 10 reviewer Ursus Maximus ISBN 0321112547 summary How to use Python to process text.

As you probably know, there are many good introductory texts about Python. This is not one of them, for this is an advanced book, but not an inaccessible one. David Mertz has a unique style and focus that we have become familiar with from his series of articles on the IBM Developer Network. Dr. Mertz is more interested in facilitating our learning process than in lecturing us, and rather than fill his pages with impressive examples designed to illustrate his expertise, he gently guides us by offering subtle yet important examples of code and analysis that makes us think for ourselves.

He has a special talent for programming in the functional style, and this is a great introduction to that style of Python programming. Thus, this is also a good guide to using the newer features introduced into Python in the last few revisions, which often facilitate the functional style of programming.

The text includes, in an appendix, a 40 page tutorial covering the basic Python language. This tutorial is, like the book, unique in its approach and is worthwhile even for experienced Pythonistas, as it sheds light on some of the underlying ideas behind the syntax and semantics, and it also illustrates the functional style of programming, which is sometimes quite useful when doing text processing. And, despite its many other virtues, this is a book about text processing.

Chapter 1 covers the Python basics, but with a particular eye towards those features most critical and useful for text processing. Chapter 2 covers the basic string operations as found in the string module and the newer built-in string functions. Chapter three is about Regular Expressions, and, although I am shy about regexes because of their relative complexity, I am very glad to have read this chapter and will no longer be intimidated when regexes are the correct approach to take! Chapter 4 is on Parsers and State machines, which are important for processing nested text, as in everyday HTML, XML and the like. This chapter is not as esoteric as its title may sound to relative newbies (like myself), as it does offer useful ideas and principles for dealing with HTML. How much more useful can a topic be than that? It is true that a deep understanding of this subject may be beyond myself and other relative duffers, but this chapter has much to offer those like me and I am sure much more to offer professionals.

Chapter 5 is on Internet tools and techniques, and this a good example of how text processing touches every important area of computer programming. We manipulate text for email, newsgroups, CGI programs, HTML and many other aspects of net programming. A good summary of XML programming is included, as well as useful synopses of other Python internet modules, from a text processing point of view.

Appendix A is the aforementioned selective and short review of Python basics. Appendix B is a ten page Data Compression primer that is quite educational. Appendix C offers the same good service for Unicode, and Appendix D covers the author's own software, a state machine for adding markup to text, which is backed up by his extensive web site that has a lot of free software to support those doing extensive text processing. Lastly, Appendix E is a Glossary for technical terms from the book. This is very much an educational book, and would be suitable for classroom work at the University level, beyond the introductory programming level; in fact, as part of a curriculum to teach programming using Python at the University level, this would be an excellent text for the second course.

One of the highlights of the book is that each chapter is concluded with a problem and discussion section. These are of the highest quality I have encountered in computer texts. Rather than overwhelming the reader with a large number of problems, the author has obviously given a lifetime of thought in coming up with a few key problems that are meant to stimulate thought, creativity, and ultimately understanding and growth in the reader. I will be coming back to the problems often, as they cannot be absorbed quickly anyway; they require thought. These would be most useful in a classroom environment; but as they are accompanied by excellent discussion material, and backed up by the author's web site, the individual reader will be well served also.

The book is more than the sum of its parts. It will be a most useful reference source for when I am doing various text related tasks for some time to come, and it was also a delightful and educational quick read in the here and now. It also amply illustrates the centrality of text processing in all areas of computer science, and I am confident that the book will be useful and educational for all programmers, whatever their area of expertise.

To sum it all up, this book is educational. It is also beautifully bound and printed, and excellently written. I rate it five stars, my highest rating, and heartily recommend its purchase.

You can purchase Text Processing with Python from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Dark Paladin writes "Recently, I asked readers to recommend some good books that were out there. There were crows for the usual crowd, like Terry Pratchet, Nail Gaiman, David Eddings, Terry Brooks, so on and so forth. But one name that kept coming up over and over again as a "must read" was R. R. Martin and the book "A Game of Thrones". So after the umpteenth "you've got to check it out or I'll burn your hat", I decided to give it a shot. And discovered one of the best read fantasy novels I've read in a decade. The story is your base fantasy stuff - "long ago, some bad things happened, but things are good - but watch out - the bad times are coming again!" Read on for the rest of his review. A Game of Thrones (A Song of Fire and Ice #1) author R. R. Martin pages 807 publisher Bantam Doubleday Dell Publishing Group rating Very Good reviewer John Hummel ISBN 0553573403 summary A gritty, dirty, disturbing fantasy tale of the court intrigues in the backdrop of an upcoming war.

But Martin does it by focusing not on one main character, but on a whole slew of them, each chapter a view from their perspective as events rage around them. Mainly around the Stark family, who's patriarch, Eddard Stark, is the Lord of Winterfell, a country to the far north who's job it is to keep up the Wall - think "Great Wall of China", only make it out of ice and stone. The Starks put a lot of stock in honor and duty, concept that must serve them well to survive a world where summers can last for years - and the winters even longer. Eddard has known war and battle once in his lifetime, when he and his best friend Robert lead an army to overthrow the Mad King almost a generation ago. Now, with his 5 children and 1 bastard child, he looks forward to a life ruling his castle in peace and training the next generation to be Starks.

Or he would, but when Robert comes calling asking Eddard to become the "Hand of the King", Eddard and his family are put into a living chess match, where loyalties shift like chameleon color, and sometimes, the pieces are lost forever. And with all the court intrigues, something dark, magical, and deadly hovers in the background, like an avalanche about to fall without warning.

What makes Martin's writing so compelling is his ability to tie us into a fictional world as fully realized as our own. It's a gritty and disturbing world, where royal families can marry brother to sister to keep bloodlines pure, Mongolian horde empires have their own brand of laws and morals, and a joust is as celebrated as a professional wrestling match - and far more dangerous. He does have a tendency to go overboard in describing the littlest detail of what armor one person is wearing and how it gleams in the sun with cloaks as soft or supple as sin (I think he used that phrase around 3 times in the book, and it was old the 2nd time), but its also those little attention to details that makes the world breath.

But more than his descriptions of the places and events are his writings about people. As I mentioned, each chapter is written from the point of view of a different character, so you get the perspective of Arya, the tomboy princess on moment, the next the view of Tyrion the Imp, dwarf (physically, not Ghimli) who's royal family opposes the Starks and reaches for the crown. Each character has their own strengths and weaknesses, things you love them for and things you hate them for. And as they interact with each other, you can see all the chess pieces on the board moving, wheels within wheels spinning as Martin brings you closer into the story, making you feel a connection with each of them - even the ones you are certain are less than moral or good. He also has no compunction about killing off main characters, which means you can't trust that the "Good Guys" will make off all right in the end.

It's a book about the love of family, how it can be twisted into something terrible and ugly, or used as a tie that binds together. It's a story about the price of honor, duty and loyalty, and what those words actually mean. It's a great book, and I'm eagerly looking forward to trying out the rest of the books in this series to see if they keep up the excellent quality of this one.

You can purchase A game of Thronesfrom bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

jkauzlar writes "When thinking about a software product's architecture there are two viewpoints to consider: the marketecture (or the marketing architecture) and the tarchitecture (the technical architecture). Oftentimes an architecture is designed without consideration of the market toward which the product is directed and even a technically superior product can fail against competitors with an inferior product, but who understand the market a lot better." This book tries to remind programmers (and managers) about maintaining the right balance of these things; read on for the rest of jkauzlar's review. Beyond Software Architecture author Luke Hohmann pages 314 publisher Addison-Welsey rating 5 out of 5 reviewer Joe Kauzlarich ISBN 0201775948 summary A software architect's guide to designing software with the market and end-user in mind

Overview Beyond Software Architecture explains how to bridge the gap between the marketecture and tarchitecture- how to create a product that not only performs well, but which also appeals to the market. It is part of the Addison-Wesley Professional Series line of books (also containing notable titles like Design Patterns, Refactoring, and Patterns of Enterprise Architecture) but this latest installment in the series is (thankfully) paperback, so it comes at a paperback price ($39.99 USD).

I am a software developer with no marketing background who works in small development teams, usually in an open-source development atmosphere. I was excited to find this book because it told me what I need to consider for my projects to help them reach the intended user. There is a lot of helpful information in this book, and at times it almost seems to suggest more work than I can handle, but I think it will ultimately pay off to be able to use the knowledge gained.

Table of Contents Forwards by Martin Fowler and Guy Kawasaki
1. Software Architecture
2. Product Development Primer
3. The Difference between Marketecture and Tarchitecture
4. Business and License Model Symbiosis
5. Technology In-Licensing
6. Portability
7. Deployment Architecture
8. Integration and Extension
9. Brand and Brand Elements
10. Usability
11. Installation
12. Upgrade
13. Configuration
14. Logs
15. Release Management
16. Security
Appendix A. Release Checklist
Appendix B. A Pattern Language for Strategic Product Management

Organization by chapter: Chapters 1-3 set up the rest of the book, defining the scope of the book as well as concepts and key terms used throughout the book. They describe a product development cycle, the players involved, etc.

The remaining chapters each focus on a particular aspect of a software product and how it relates to both the customer and the product's architecture. Catalogs of alternatives are available for each topic along with caveats for each alternative.

For example, in Chapter 6, "Portability," the advantages and disadvantages of creating a portable application are discussed. If most of your customers are using Windows and your code is written in C++, then the cost of supporting Solaris as well may be the difference between a product's financial success and failure. The chapter reminds us that guaranteeing support for 6 operating systems and 4 database backends and 3 browsers means that we have to support and provide quality assurance for 6x4x3=72 combinations of products. Then it describes a process of eliminating or prioritizing combinations of platform support. The chapter goes on to describe ways in which a product's architecture can affect its portability and how best to write software to be portable.

Related to this is a discussion of how supporting particular platforms ties your release cycles into the release cycles of products you support-- another problem that can financially doom a project. Another point from Chapter 6 that I found interesting was what it means to support a platform-- the customer expects you to take advantage of the platform's features. Many cross-platform products are written to be identical on each platform they support, which means they probably ignore platform dependent libraries or features that can enhance performance or usability. This creates a potential place where competitors can gain an edge.

So you see each chapter goes into great length and detail to cover the nuances of its topic, and it is extensive enough that it can be overwhelming and even discouraging.

Who should read this book Anyone involved in software architecture or design, particularly project managers, whether in a very small group or a large corporate atmosphere. Open source developers are notoriously technically proficient, and often are not marketing-savvy. Oftentimes you have to be technically proficient to even install and use an open-source product. Ordinary developers who do not participate in architecture might benefit from reading this book in order to understand the decisions being made by the architects.

Why someone should read this book Many software industry professionals are not marketing experts and may even view the marketing department as their enemy. This book helps bridge that gap between marketing and project management, helping the two parties work together to create more effective, usable, or profitable software. Similarly, open-source developers usually architect and market their own software. Tactics described in this book could help OS developers create software that lasts longer, is more extensible, and more usable.

What this book is and is not. This is a general, and not technology-specific, guide to designing software and while doing so, keeping a marketing perspective in mind. It describes what things a software architect should remember when designing a product.

It is not a guide to marketing software. It does not recommend particular solutions for particular problems. It does not tell you what you should do, only what the consequences of your choices may be.

What I would like to see A similar book that concentrates on the open-source aspects of the topics included in this book and how and how not to use open source tools (like Freshmeat, Sourceforge, Bugzilla, CVS) for marketing and maintaining successful open-source projects.

Recommendation Buy this book if you have benefited from Design Patterns, Refactoring or Patterns of Enterprise Architecture. This book is a welcome addition to a line of books that has consistently contributed to the standard knowledge base of the software architecture discipline.

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

ProfKyne writes "I was excited to read this book when I first noticed it listed as "coming soon" in the Java section of O'Reilly's site back in May. I downloaded and read the sample chapter and waited expectantly for the book to be released. I was hoping that this book would be perfect for me, as nearly all of the Java programming I have done has dealt in some way with database access, though I do not consider myself to be an expert on the subject. The book didn't disappoint; Java Database Best Practices is an excellent high-level guide to writing database-driven applications from Java." Read on for the rest of ProfKyne's review. Java Database Best Practices author George Reese pages 267 publisher O'Reilly Associates rating Excellent for Java programmers moving to J2EE reviewer Erik Price ISBN 0596005229 summary A high-level introduction to writing database-driven apps in Java

What it's about: The book is divided into three sections of several chapters each:

1. Data Architecture - an introduction to database-driven application concepts
2. Persistence Fundamentals - descriptions of the various persistence frameworks for Java application development
3. Tutorials

I should note that the book follows a strange order: the most logical progression for the apparent target audience of this book (developers just getting into J2EE) would be to read Part 1 first, then Part 3, and then Part 2, as the "Persistence Fundamentals" section draws heavily on content introduced in the later "Tutorials" section.

The first section (Data Architecture) introduces some of the concepts that will be covered in greater depth later on in the book, but also contains an excellent chapter, "Relational Data Architecture," on database schema design and normalization. By the way, this is the sample chapter that can be downloaded from O'Reilly's site. In fact, this chapter set itself apart from the rest of the book in that it goes into a great deal of detail on its subject (although obviously an aspiring DBA should probably read whole books dedicated to the topic of relational database concepts). Most of the rest of the chapters in the book is somewhat more lightweight than "Relational Data Architecture." This section also contains a chapter that introduces some of the things to be aware of when managing transactions, including implementation tips on using transactions in JDBC programming such as optimistic locking and the various transaction types (dirty reads, etc).

The Persistence Models section focuses on different persistence frameworks, there is a chapter for each of the following: Persistence Fundamentals, EJB Container-Managed Persistence (covers 1.x and 2.0 models), EJB Bean-Managed Persistence, JDO, and "Alternative Persistence." The fundamentals chapter is where some of the best of the "best practices" of the book are found, and introduces such patterns as the Data Access Object pattern and the Memento pattern in the context of a simple guest book JSP application. The EJB chapters do assume that the reader has a basic understanding of how EJB works, and provides suggestions and guidance on ways to implement EJBs in real J2EE applications. (Don't worry, if you don't know about EJBs, the J2EE Tutorial chapter later in the book provides this.) The JDO section is one of the shortest in the book; I think that it's just such a new technology (in terms of available implementations) that most of the "best practices" are yet to be discovered. "Alternative Persistence" means Hibernate and Castor.

The Tutorials section is definitely not for advanced Java programmers, as it contains beginner-level introductions to the J2EE platform, the SQL language, the JDBC architecture, and the JDO API. If you really don't know anything about JNDI or servlets or EJB, then the J2EE chapter is written for you -- it's not a "how-to" tutorial, but rather a description of the basic concepts. The JDO tutorial is like the J2EE tutorial, introducing the basic concepts such as "the extent" and the filter language used to query for JDO-persisted objects, but I think partly because it's such a new technology, there's not a lot of detail here. You'll still have to read more about J2EE EJB, or JDO, if you decide to use them in a production application. On the other hand, you will learn how to make effective use of SQL queries and the JDBC API (which lets you execute SQL queries from your Java code) from their respective tutorials.

While this is a good start, you will eventually want something more in-depth than this if you are actually implementing a J2EE application (such as a book dedicated to servlet/JSP programming or Enterprise JavaBean development). But I really wish that I had read Java Database Best Practices before tackling these subjects, as it would have helped ease the transition

What's to like As strange as it may sound, one of the things I liked most about the book is that it is relatively thin. In other words, the author gets right to the point and doesn't waste excessive space replicating information that can be found elsewhere. For instance, when describing how to implement a database-independent sequencing component, he incorporates enough code to support what he's saying, but doesn't include page after page of complete code listing, intact with multi-line Javadocs and plenty of whitespace -- just the meat. You can download all of the code from O'Reilly's site in a zip archive (and yes, it does include the Javadocs and whitespace that are wisely omitted from the book). Ironically, the book costs no less than other offerings from O'Reilly that are twice as thick.

Also, the "best practices" in the book are very good and, at least in my case, I was not familiar with some of them, so it was very worthwhile reading. As an example, I myself have recently run into the problem of different sequencing systems on different databases (such as MySQL's AUTO_INCREMENT column type vs PostgreSQL's sequence types). I've worked around it by modifying the application's database calls, but that isn't really a good strategy. Implementing a sequencer at the application level (one of the "best practices") is a much better idea if you're not clustering your application servers and other applications will not be performing INSERTs into the database. On the other hand, if clustering is an issue, then it's probably a better idea to use EJBs, and if other applications will be writing to the data store, then database portability will be difficult in the first place (even with the help of Perl's DBI or PHP's PEAR DB abstraction). Some of the other excellent best practices introduced are the DAO pattern and database schema normalization coverage.

What's to consider The most important thing to know when considering this book is that it really struck me as being appropriate for novice J2EE developers and/or those who are new to database programming in general. First of all, I think it's safe to assume that most people who will be doing anything with databases in Java will be using at least some element of the J2EE platform, and this book makes that same assumption. Java's tremendous success right now is in server-side application development. This means there won't be as much useful information in this book for the folks who are writing, say, an AWT interface tightly coupled to a MS-Access database through ODBC calls. Second of all, the patterns and practices described in this book should be familiar to most people who are already architecting J2EE applications, and are covered in greater depth in other books on enterprise application development.

Having now covered the main consideration, I do have to pick a couple of nits. Firstly, this book does suffer from a few of the editing problems that plague nearly all computer books (yes even the O'Reilly books) in their first printing. It's kind of embarrassing, but even in the sample chapter I found a somewhat bizarre mistake near the end, where a class diagram is drawn up using ERD notation instead of UML. Fortunately, there aren't too many technical errors like this. Another bone to pick was the author's choice to use a hideous scriptlet-heavy JSP instead of a servlet forwarding to a JSP in the small Guest Book application in "Persistence Fundamentals." I know that this is Java Database Best Practices, not Java Model View Controller Best Practices, but scriptlets are both difficult to read and quite frankly scorned as J2EE moves toward JSTL and JSP 2.0. It's a little too bad that View and Controller are mixed up in this example, because the author does an excellent job of explaining how to implement the Model using the Data Access Object pattern.

Finally, I have a feeling this book was named "Java Database Best Practices" for marketing reasons, perhaps to go with O'Reilly's other offering, "Java Enterprise Best Practices". While this is an excellent book about Java database programming, and there are indeed dozens of "Best Practice" tips strewn throughout the book, I think a better name for this book would have been "Java Database Fundamentals."

The summary I didn't want to simplify and rehash the book's "best practices" contents in this review, but rather provide prospective readers with an idea of what to expect from this book. Personally, I got a lot out of the book, but if you've already implemented bean-managed persistence in your EJBs using JDO, then you've probably already gotten past the point where this book is going to be a big help. In your case, it might be worth having around the office if you can get the company to pay for it. However, for those who have learned the Java language and want to get more involved in server-side application development, you're going to want to make sure you're familiar with all of these concepts and this book is the perfect way to get started with that. Where to find more info I'm not going to replicate the table of contents or any of the content in the book, because all of that information as well as the excellent sample chapter are available from O'Reilly's site. I purchased the book from SoftPro Books in Massachusetts (US), a bookstore for computer geeks. This is a good place to peruse the book if you're still riding the fence.

You can purchase the Java Database Best Practices from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Trevor Stow writes with the review below of Ellen Ullman's The Bug. "The Bug is about a programmer, Ethan Levin, at a software start-up in the mid-1980s, tracking down one particularly irksome bug in his own C code. The longer this bug eludes Ethan, which his co-workers start calling the 'The Jester,' the more destructive its effects on his personal life. The Jester is this story's villain, one that can't talk, eat, get tired, or be reasoned with." Read on for the rest of Trevor's review. The Bug author Ellen Ullman pages 368 publisher Doubleday rating 8.5 reviewer Trevor Stow ISBN 0385508603 summary A programmer 's life unravels as he struggles to find a bug.

In fact, The Jester seems to have an impish intelligence of its own, laying dormant for weeks somewhere deep in the libraries of the company's ground-breakingly new GUI front end. When it does surface, it's usually during a sales presentation, causing a complete system failure: garbage on the screen, frozen keyboard. It's enough to frighten any and every potential customer. For a start-up still living on venture capital funding, this is a bad thing.

As if the stakes weren't high enough, our hero, Ethan, isn't exactly a well-rounded Renaissance Man. He has a single friend at the office, and they barely talk. Otherwise, Ethan is irritable, distant, and often loses himself in his own logic-gated thoughts. He suffers moments of mild panic where he doubts his own competency and frets over not having an advanced degree. Plus, his fellow coders are a petty, snide-commenting bunch; meetings degrade into profanity-laden shouting matches, passing the blame, etc, all of which spurs Ethan to work harder. He autopilots through dinner while reading a Unix manual, works from home, and falls asleep in his clothes.

None of this leaves room for Ethan's girlfriend, Joanna. At the story's beginning, she goes to India for a month with her male friend Paul. Ethan can't go, citing the importance of his work. Paul's wife can't go either. We see where that's heading.

Ethan's life begins to unravel. He associates his personal problems with The Jester. Once that damn bug's squashed, he tells himself, the rest of his life will stabilize into some happier space.

The story's narrator is Roberta, who speaks to us from the early 2000s, remembering her job as the QA tester who worked most closely with Ethan. Roberta does have an advanced degree, in linguistics, but jobs in academia are scarce, and what else do you do with a degree in linguistics? At first, Roberta dismisses the programmers as a gruff, dismissive pack of dorks, just as they dismiss her because she can't code. A frosty wall separates the two sides of the product development team: those who write the bugs, and those who find them. In her evenings, Roberta composes poetry and suffers her own anxiety over abandoning a higher education for a plain job in IT.

Eventually, though, Roberta learns to program in C, and that's where The Bug shines brightest, touching on some sparkling insights: the nature of life, the nature of time, the cold beauty of code, and ourselves, living side-by-side with computers that are not, alas, alive. Stuff that will stick with you.

However...

I was disappointed with the book's end. If you program for a living (as I do), you will see parts of yourself in Ethan. But hopefully, you aren't Ethan. Even if you have no friends, no girlfriend, nothing, you still might play video games or watch TV or something (read?). Ethan, it seems, makes no effort to find even brief happiness. His life is joyless. And that's probably why I didn't like the ending. The book builds so well, keeps a quick pace, with smart dialog, rich characters, suspense, and very high stakes: I felt the pay-off could have -- should have -- been much grander.

Ellen Ullman, who also wrote Close to the Machine, was a programmer in the 80s. I caught her interview on NPR, where she explained that Ethan's story and The Jester were very loosely based on her own pursuit of a bug while working at Sybase.

You'll probably enjoy The Bug, even if you don't like computers and write poetry for a living. It's adult fiction and feels contemporary without trying to be 'zany' or 'hypercharged.' It's not a funny book, but rather a calm, wise walk into unexplored story matter, with lots of interesting bits to think about.

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

tep-sdsc writes "Richard Morgan has a problem. His first novel, Altered Carbon, will be a tough act to follow. It is set in a future world that could rival Heinlein's Future History and Niven's Known Space. There's enough material here for a career, not just a (great) first novel." OK, so you know he likes it -- now read on for the rest of Tom's review. Altered Carbon author Richard Morgan pages 534 publisher Del Rey (US) rating Excellent reviewer Tom Perrine ISBN 0345457684 summary A future beyond death, through personality transplantation.

It would be easy to describe this book as "cyberpunk meets noir," but that would be a disservice to the reader, the author and the book.

Although this book is set in a future that is seems to be heavily influenced by the punk movement, with computers, hackers, weapons, and leather, this is no superficial, cartoon world setting for a quick romp through cyberspace. There is a depth and texture here that promises, and delivers, as a setting for a novel that could end up as influential as Vinge's True Names, or Stephenson's Snow Crash or Spillane's Mike Hammer.

The main technological trapping of this setting is the ability to digitize, store and transport human consciousness. Peoples' consciousnesses can, and are, digitized and loaded out of and into their bodies on a regular basis. The state uses this to punish criminals by storing their minds "in the stack" (digital prison) and the wealthy and powerful can have themselves "backed up" like yesterday's spreadsheets. Interstellar travel is via "digitized human freight." Human bodies ("sleeves") can be rented, bought and sold, to provide containers for these digitized minds. And this is just the background.

This is also a hardboiled detective thriller, easily the equal to Chandler or Hammett in both plot and characterization. There is a complex plot, the de rigueur dames and guns, but also some important themes that are surprising for the genre. The plot is never formulaic, with a depth and enough unexpected twists and turns to keep the reader guessing well into the last chapter.

The protagonist, Takeshi Kovacs, is no simple hardboiled detective; he's a cashiered UN "Envoy," qualified to do anything from holding a beach head or planning a military invasion, to taking over a government from within. People with this training are barred from public office and high government positions on most settled worlds. And Kovacs has been offered a job he can't refuse by one of the richest men in twenty planets: "Kovacs, find out who killed me."

On a deeper level, this novel asks some real hard questions, that get to the heart of what it means to be human. If you can digitize, back up and restore people, what is the meaning of death? Is the "soul" digitized, or just your memories? Does it matter? When bodies can be rented and exchanged, just what is "identity"? When people can buy new bodies and live for centuries, amassing power and wealth, how will that affect their humanity? Will they become more than human, or less? How will this effect human society? These issues are all raised subtly, this is no sermonizing sociology text masquerading as a novel.

But Morgan's novel remains at its heart a well-crafted detective story. No matter how corrupt the society, no matter how powerful the rich, in the end, justice comes from the smoking barrel of a hired gun, working for some fast cash, plus expenses. This books tries, and succeeds, on so many levels, that can only hope that this will be just the first novel from this new author. Somewhere, Chandler and Hammett are saying, "Ya' done good, kid. Now kiss the dame and get outta here."

(As I was finishing this review, I discovered that Morgan's second novel, Broken Angels, which continues Kovacs exploits, has just been published by Gollancz in the UK. I'll gladly pay international shipping to get my hands on this second book as soon as possible.)

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

tep-sdsc writes "Richard Morgan has a problem. His first novel, Altered Carbon, will be a tough act to follow. It is set in a future world that could rival Heinlein's Future History and Niven's Known Space. There's enough material here for a career, not just a (great) first novel." OK, so you know he likes it -- now read on for the rest of Tom's review. Altered Carbon author Richard Morgan pages 534 publisher Del Rey (US) rating Excellent reviewer Tom Perrine ISBN 0345457684 summary A future beyond death, through personality transplantation.

It would be easy to describe this book as "cyberpunk meets noir," but that would be a disservice to the reader, the author and the book.

Although this book is set in a future that is seems to be heavily influenced by the punk movement, with computers, hackers, weapons, and leather, this is no superficial, cartoon world setting for a quick romp through cyberspace. There is a depth and texture here that promises, and delivers, as a setting for a novel that could end up as influential as Vinge's True Names, or Stephenson's Snow Crash or Spillane's Mike Hammer.

The main technological trapping of this setting is the ability to digitize, store and transport human consciousness. Peoples' consciousnesses can, and are, digitized and loaded out of and into their bodies on a regular basis. The state uses this to punish criminals by storing their minds "in the stack" (digital prison) and the wealthy and powerful can have themselves "backed up" like yesterday's spreadsheets. Interstellar travel is via "digitized human freight." Human bodies ("sleeves") can be rented, bought and sold, to provide containers for these digitized minds. And this is just the background.

This is also a hardboiled detective thriller, easily the equal to Chandler or Hammett in both plot and characterization. There is a complex plot, the de rigueur dames and guns, but also some important themes that are surprising for the genre. The plot is never formulaic, with a depth and enough unexpected twists and turns to keep the reader guessing well into the last chapter.

The protagonist, Takeshi Kovacs, is no simple hardboiled detective; he's a cashiered UN "Envoy," qualified to do anything from holding a beach head or planning a military invasion, to taking over a government from within. People with this training are barred from public office and high government positions on most settled worlds. And Kovacs has been offered a job he can't refuse by one of the richest men in twenty planets: "Kovacs, find out who killed me."

On a deeper level, this novel asks some real hard questions, that get to the heart of what it means to be human. If you can digitize, back up and restore people, what is the meaning of death? Is the "soul" digitized, or just your memories? Does it matter? When bodies can be rented and exchanged, just what is "identity"? When people can buy new bodies and live for centuries, amassing power and wealth, how will that affect their humanity? Will they become more than human, or less? How will this effect human society? These issues are all raised subtly, this is no sermonizing sociology text masquerading as a novel.

But Morgan's novel remains at its heart a well-crafted detective story. No matter how corrupt the society, no matter how powerful the rich, in the end, justice comes from the smoking barrel of a hired gun, working for some fast cash, plus expenses. This books tries, and succeeds, on so many levels, that can only hope that this will be just the first novel from this new author. Somewhere, Chandler and Hammett are saying, "Ya' done good, kid. Now kiss the dame and get outta here."

(As I was finishing this review, I discovered that Morgan's second novel, Broken Angels, which continues Kovacs exploits, has just been published by Gollancz in the UK. I'll gladly pay international shipping to get my hands on this second book as soon as possible.)

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

tep-sdsc writes "Richard Morgan has a problem. His first novel, Altered Carbon, will be a tough act to follow. It is set in a future world that could rival Heinlein's Future History and Niven's Known Space. There's enough material here for a career, not just a (great) first novel." OK, so you know he likes it -- now read on for the rest of Tom's review. Altered Carbon author Richard Morgan pages 534 publisher Del Rey (US) rating Excellent reviewer Tom Perrine ISBN 0345457684 summary A future beyond death, through personality transplantation.

It would be easy to describe this book as "cyberpunk meets noir," but that would be a disservice to the reader, the author and the book.

Although this book is set in a future that is seems to be heavily influenced by the punk movement, with computers, hackers, weapons, and leather, this is no superficial, cartoon world setting for a quick romp through cyberspace. There is a depth and texture here that promises, and delivers, as a setting for a novel that could end up as influential as Vinge's True Names, or Stephenson's Snow Crash or Spillane's Mike Hammer.

The main technological trapping of this setting is the ability to digitize, store and transport human consciousness. Peoples' consciousnesses can, and are, digitized and loaded out of and into their bodies on a regular basis. The state uses this to punish criminals by storing their minds "in the stack" (digital prison) and the wealthy and powerful can have themselves "backed up" like yesterday's spreadsheets. Interstellar travel is via "digitized human freight." Human bodies ("sleeves") can be rented, bought and sold, to provide containers for these digitized minds. And this is just the background.

This is also a hardboiled detective thriller, easily the equal to Chandler or Hammett in both plot and characterization. There is a complex plot, the de rigueur dames and guns, but also some important themes that are surprising for the genre. The plot is never formulaic, with a depth and enough unexpected twists and turns to keep the reader guessing well into the last chapter.

The protagonist, Takeshi Kovacs, is no simple hardboiled detective; he's a cashiered UN "Envoy," qualified to do anything from holding a beach head or planning a military invasion, to taking over a government from within. People with this training are barred from public office and high government positions on most settled worlds. And Kovacs has been offered a job he can't refuse by one of the richest men in twenty planets: "Kovacs, find out who killed me."

On a deeper level, this novel asks some real hard questions, that get to the heart of what it means to be human. If you can digitize, back up and restore people, what is the meaning of death? Is the "soul" digitized, or just your memories? Does it matter? When bodies can be rented and exchanged, just what is "identity"? When people can buy new bodies and live for centuries, amassing power and wealth, how will that affect their humanity? Will they become more than human, or less? How will this effect human society? These issues are all raised subtly, this is no sermonizing sociology text masquerading as a novel.

But Morgan's novel remains at its heart a well-crafted detective story. No matter how corrupt the society, no matter how powerful the rich, in the end, justice comes from the smoking barrel of a hired gun, working for some fast cash, plus expenses. This books tries, and succeeds, on so many levels, that can only hope that this will be just the first novel from this new author. Somewhere, Chandler and Hammett are saying, "Ya' done good, kid. Now kiss the dame and get outta here."

(As I was finishing this review, I discovered that Morgan's second novel, Broken Angels, which continues Kovacs exploits, has just been published by Gollancz in the UK. I'll gladly pay international shipping to get my hands on this second book as soon as possible.)

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

tep-sdsc writes "Richard Morgan has a problem. His first novel, Altered Carbon, will be a tough act to follow. It is set in a future world that could rival Heinlein's Future History and Niven's Known Space. There's enough material here for a career, not just a (great) first novel." OK, so you know he likes it -- now read on for the rest of Tom's review. Altered Carbon author Richard Morgan pages 534 publisher Del Rey (US) rating Excellent reviewer Tom Perrine ISBN 0345457684 summary A future beyond death, through personality transplantation.

It would be easy to describe this book as "cyberpunk meets noir," but that would be a disservice to the reader, the author and the book.

Although this book is set in a future that is seems to be heavily influenced by the punk movement, with computers, hackers, weapons, and leather, this is no superficial, cartoon world setting for a quick romp through cyberspace. There is a depth and texture here that promises, and delivers, as a setting for a novel that could end up as influential as Vinge's True Names, or Stephenson's Snow Crash or Spillane's Mike Hammer.

The main technological trapping of this setting is the ability to digitize, store and transport human consciousness. Peoples' consciousnesses can, and are, digitized and loaded out of and into their bodies on a regular basis. The state uses this to punish criminals by storing their minds "in the stack" (digital prison) and the wealthy and powerful can have themselves "backed up" like yesterday's spreadsheets. Interstellar travel is via "digitized human freight." Human bodies ("sleeves") can be rented, bought and sold, to provide containers for these digitized minds. And this is just the background.

This is also a hardboiled detective thriller, easily the equal to Chandler or Hammett in both plot and characterization. There is a complex plot, the de rigueur dames and guns, but also some important themes that are surprising for the genre. The plot is never formulaic, with a depth and enough unexpected twists and turns to keep the reader guessing well into the last chapter.

The protagonist, Takeshi Kovacs, is no simple hardboiled detective; he's a cashiered UN "Envoy," qualified to do anything from holding a beach head or planning a military invasion, to taking over a government from within. People with this training are barred from public office and high government positions on most settled worlds. And Kovacs has been offered a job he can't refuse by one of the richest men in twenty planets: "Kovacs, find out who killed me."

On a deeper level, this novel asks some real hard questions, that get to the heart of what it means to be human. If you can digitize, back up and restore people, what is the meaning of death? Is the "soul" digitized, or just your memories? Does it matter? When bodies can be rented and exchanged, just what is "identity"? When people can buy new bodies and live for centuries, amassing power and wealth, how will that affect their humanity? Will they become more than human, or less? How will this effect human society? These issues are all raised subtly, this is no sermonizing sociology text masquerading as a novel.

But Morgan's novel remains at its heart a well-crafted detective story. No matter how corrupt the society, no matter how powerful the rich, in the end, justice comes from the smoking barrel of a hired gun, working for some fast cash, plus expenses. This books tries, and succeeds, on so many levels, that can only hope that this will be just the first novel from this new author. Somewhere, Chandler and Hammett are saying, "Ya' done good, kid. Now kiss the dame and get outta here."

(As I was finishing this review, I discovered that Morgan's second novel, Broken Angels, which continues Kovacs exploits, has just been published by Gollancz in the UK. I'll gladly pay international shipping to get my hands on this second book as soon as possible.)

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

Peter Wayner writes: "If you're a handicapped Windows user, Microsoft offers suggestions and assistance -- but XBox users were out of luck until Andrew 'Bunnie' Huang finished his book Hacking the XBox. Don't be fooled by the title. Officially, Huang's excellent book is not about helping the differently-abled. That would be against the law. Huang was forced by the DMCA to hide his humanitarianism under the cloak of 'reverse engineering' because this is one of the few legitimate uses given a small amount of protection by the law. But if you've got an urge to help the handicapped or any other reason to tinker with your XBox, buy this book before the Man sees through this ruse." Read on for the rest of Peter's review. Hacking the XBox author Andrew "Bunnie" Huang pages 288 publisher No Starch Press rating 9 reviewer Peter Wayner ISBN 1593270291 summary How and why to crack the seal on your Xbox.

There are many reasons why you might want to take apart your XBox, but one of the best ones I can imagine is making it easier for people who can't see, hear or move too well to play the same video games as the rest of us. Searching Microsoft's web site for documents containing both "handicapped" and "xbox" reveals only a suggestion for how to change the degree of difficulty of your Zoo Tycoon Game.

Someone who might want to retrofit a new pointing device or some other enabling gadget onto the XBox might start with the chapter describing how to fix a real USB cable onto the XBox. The chapter, like most in the book, is heavily illustrated with step-by-step pictures and instructions for clipping the cables in the right place and soldering them back together. Some of this might seem a bit rudimentary, but the detail can't hurt. In many cases, the real challenge is finding a way to take apart the case or the pack of wires in the right way. Smashing it isn't always an option. This is a book about mathematics, electronics, and taking apart plastic boxes.

Alas, just doing a bit of soldering isn't going to be enough unless you can make the right drivers. To help those who might want to reprogram their XBox, Huang devotes much of the book to stripping away the layers of the XBox security system, a story that is part mystery and part journey through the security layers in the system. The book is arranged in a very roughly chronological order. While it is mainly a book that teaches you how to reverse engineer the XBox, it is also a story of how he overcame the obstacles presented by the encryption. He talks as much about the unsuccessful paths as the ones that paid off. (This is, I think, an ideal model for the scientific community. It's much more educational than the terse papers that present the results as fait accompli.)

This part of the book quickly gets quite complicated, because Microsoft obviously tried hard to produce a secure machine that could provide a fair platform for people to play games. Getting the XBox to run any old software is not an easy task, but Huang describes several major techniques for drilling through the various layers of security. Again, he offers detailed pictures and instructions for construction special tools that snarf signals from a bus. Then he explains how he managed to grab the right keys for decrypting some of the most important data. Although it's a technical book, it unfolds like a spy novel.

The book is also very politically thoughtful. While the clueless will equate the word "hacking" in the title with piracy, money laundering, terrorism, and not phoning home on mother's day, Huang frames every step with a discussion of whether it is motivated by good or evil. He's not interested in building a tool to pirate XBox games and points out that many of the modifications aimed at running Linux on the Xbox do not help the pirates in any way. If anything, they make the games entirely unplayable.

Huang does want to defend the right to tinker, citing Ed Felten and others in a defense of something we're rapidly losing. I've heard horror stories from Army Majors about Windows PCs that refused to boot after failing to find a C drive. Do we really want to build machines that can't be retrofitted or fixed in the field? Many war movies are saved by the young private who (like Huang) is willing and able to tinker.

If you don't respond to pulls on the heartstrings, you might want to read one of the concluding chapters from the EFF's Lee Tien about the current legal climate. There are few exemptions for tinkering and many of them are limited. Reverse engineering is okay if you're a big corporation making a competing product, but that didn't help 2600 magazine when they were accused of trying to help people view DVDs on their Linux machine. I can only imagine what they would do to someone with very bad vision who wanted to enable a special zoom feature on their Xbox.

The book was originally going to be published by Wiley, but the company balked when it realized there were stiff legal penalties for helping handicapped people use computers. Even the Massachusetts Institute of Technology felt that it would be better for Huang to disassociate itself from Huang and his humanitarian efforts. The university only relented after pressure from a few good professors who helped the university understand the value in Huang's mission. Huang decided to publish the book himself with the help of his girlfriend, Nikki Justis. The two of them should be commended for turning out such a beautiful, professional book. If you're intrigued by the xbox, interested in helping the handicapped, or just trying to learn how to reverse engineer things before things get worse, check out this book. It's a wonderful contribution to the literature.

To close, I'm offering a pair of cool projects with the hope that Huang's book will inspire people to tinker:

• Sonic Information -- The sound in games like Quake is pretty good, but what if it was rendered with enough precision to let blind people grok the scene? The echoes from the tapping of a white cane already carry plenty of information to the blind. What if they could compete on an equal footing with the sighted? Who would win?
• Eye Movement Measuring tools -- Tools exist for sensing the position of our eyes. A quadriplegic game could just look in the right direction and shoot. Clearly some work would need to be done to encode all of the shift-left-left-down-right maneuvers from the games. This could help all of us. The thumb you save from repetitive motion injuries could be your own.

Note: Since this review was written, Hacking the Xbox has found a publisher in the form of No Starch Press. The original self-published version will probably be a sought-after collectable ;)

Peter Wayner is the author of Translucent Databases and ten other books. None rely on the DMCA. Hacking the Xbox is due in July at bn.com; you can also go directly to the book's page at No Starch Press. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Scott Abel writes "Itâ(TM)s no secret. To win at business, you must perform better than your competition. Better. Stronger. Faster. You get the picture. In Managing IT as an Investment: Partnering for Success, Ken Moskowitz and Harris Kern explore how changing the way you think about IT can help you develop solutions that exceed your strategic goals. To achieve the highest levels of profitability, the authors say, IT organizations must be well-tuned and in alignment with the goals of the enterprise to which they belong." Read on for the rest of Scott's review. Managing IT As An Investment: Partnering for Success author Ken Moskowitz, Harris Kern pages 150+ publisher Prentice Hall PTR rating 9 reviewer Scott Abel, Content Management Strategist ISBN 013009627X summary How changing the way you think about IT can help you develop solutions that exceed your strategic goals.

For far too long, the authors argue, IT has been incorrectly viewed as a separate part of the enterprise; a distant silo, relegated to the status of a âoecost center.â Instead, the authors make the case for transforming IT into a âoevalue centerâ â" a mission-critical member of the business enterprise, managed as a strategic asset.

In order to get there -â" and to maximize IT value -â" the authors say organizations must realize that âoeIT is inseparable from the business and requires complete alignment with business goals.â Then, they have to admit that thereâ(TM)s âoeno such thing as an IT project.â

âoeIT is no longer a cost center and a growing number of highly successful firms are recognizing this,â the authors say. âoeIT is an investment and should be managed as such to increase revenue and profits. No matter what size project, IT is a member of the business team and should be accountable and responsible.â

Getting past old-world ways of thinking can be difficult for business and IT-minded folks alike; such transformations are often riddled with unexpected organizational change management issues. Moskowitz and Kern do a nice job of exploring some of these difficulties at a high level, but leave plenty of room for in-depth exploration by other authors.

They introduce readers to âoeConsequence-Based Thinkingâ in Chapter 2, a concept that promotes decision-making based on desired business results, rather than on the IT problems you face. The authors explore ways you can avoid âoethe Right/Wrong trapâ (situations in which humans forfeit the desired consequences for the privilege of being right), develop jointly produced business cases (âoea technology case is not sufficientâ), and help each department in your organization contribute to the success of the enterprise mission.

In Chapter Three, âoePartnering,â the authors illustrate the importance of creating a team that will support the goals of the enterprise. âoeIt is key that members of IT teams see themselves and their work as core to the business itself, and not view the IT function as an appendage of the business.â As this happens, the authors say, âoeothers will view them (IT) as critical and necessary partners that can be trusted to provide solutions that donâ(TM)t merely serve a process, but truly serve business outcomes.â

Business partners must change the way they think of themselves as well. Business must think of itself as âoea partner with, rather than a customer of IT,â the authors say. They recommend the development of formalized contracts that spell out responsibility and accountability for all involved; a âoecommon vocabularyâ (to help get everyone in your organization, regardless of role, on the same page); and provide words to the wise for management: âoemanagers will never have as much information as people on the front line.â

Sizeable emphasis is placed on the importance of jointly developed business cases, which the authors say, âoeforces IT and business to engage in continuous dialog in order to ensure success.â Jointly developed business cases can help align IT with business objectives, and have the additional benefit of âoemoving the business agenda forward and creating partnerships and understanding.â A sample Business Case template is provided as an appendix.

Chapter Five, âoeStrategyâ makes the case for building a big-picture strategy that âoestresses an enterprise point of view over seat-of-the-pants, silo thinking.â Organizations without an enterprise strategy often end up creating what the authors call âoeislands of automationâ that will later need to be integrated.

Strategic thinking is a skill and not something that comes easily. It involves adopting new processes and changing the way we think about our jobs. By adopting a âoeBusiness Strategy Formation Processâ that relates an enterprise-to-an-individual and an individual-to-an-enterprise, the authors say organizations can make âoeconsistent decisions that incorporate foresight.â

Chapter Six, âoeThe Small Picture,â provides guidance on communicating the âoebig pictureâ to âoesmall pictureâ folks by answering the question: âoeWhatâ(TM)s in it for me?â Chapter Seven discusses ideas for setting up and managing IT departments as âoevalue centersâ while Chapter Eight, âoeHuman Capital Managementâ deals with issues of people management, individualism, and job satisfaction.

Chapter Nine, âoeInvesting In Values,â provides a brief overview of the importance of values, which the authors define as the âoeguiding principles and basic beliefs that are fundamental assumptions on which subsequent actions are based.â The authors provide several models to help you make which value decisions. They also discuss how to reap âoethe hidden harvestââ"the rewards delivered through collaborating with others toward a common, understood and measurable goal, benefits not realized through traditional, inside-the-box thinking.

While Managing IT as an Investment is indeed a value-added resource, reading the book is not enough. Youâ(TM)ll need to do a little homework before you go tackling a major change in your organization. Youâ(TM)ll need additional guidance not provided in the book to help you decide whether your IT and business staffs should work in the same physical space to help reduce communication barriers and establish a sense of âoeteamâ; if you should re-organize your management structure so both IT and business team members report to the same manager; how you should communicate information about your project in order to create project evangelists; and whether your reward structure needs some revamping (is IT currently rewarded for âoeon timeâ delivery as opposed to delivery of quality solutions that deliver the highest return on investment possible?).

Despite these weaknesses, Managing IT as an Investment: Partnering for Success is an excellent addition to both business and IT literature. At only 150+ pages â" 10 chapters, followed by 4 value-added appendices â" you can read the entire book in an afternoon. The book is well worth the effort. Includes case study information and references to other published works. Perfect for those involved in paradigm-shifting projects where strengthening the relationship between IT and business can help ensure success.

Scott Abel is a content management strategist. Look for his column, The Content Wrangler, on ePrairie.com. You can purchase the Managing IT As An Investment: Partnering for Success from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

gianluca writes "Having always been a heedful guy, I always duly did my homework, going through the lengthy manual pages of a number of regular expressions (regex) crunching tools. You name it: be it PERL, awk, emacs, sed or even one of the .NET framework languages -- any such program provides support for the same regex expressions (or at least, so they seem to the occasional observer). After some years of regex practice with these tools, I had the pretentious conviction that I knew my way through the intricacies of patterns, grouping, greediness, and the like. When I first stepped into Mastering Regular Expressions, looking at the nearly 500 pages which build up Friedl's book, I wondered what could someone ever have to say about regexes to fill so many pages." Gianluca ended up finding plenty of worthwhile content; read below for his review. Mastering Regular Expressions, 2nd edition author Jeffrey E. Friedl pages 460 publisher O'Reilly rating 9.5 reviewer Gianluca Insolvibile ISBN 0596002890 summary An in-depth guide to lead the apprentice to mastering regular expressions' wizardry

My first suspicion, I admit, was that I was facing one of the countless "man page reprints" that you find these days. It was only after reading the book that I eventually understood: before then, I had had no idea of what regexes were really about.

What it's about The book is logically divided into three parts: the first one (Chapters 1, 2 and 3) introduces the reader to the basic concepts of regexes, building a common ground upon which the subsequent chapters will be based. The introduction is clear and straightforward, and lets the readers quickly grasp the key points in the regex business. This part is more or less a good summary, presenting information that can be found also in existing manual pages (albeit presented in a distilled form, which lets you perceive that the author has very clear ideas about the matter). If you already know something about regexes, you could skip this part entirely -- even if reading it turns out to be a nice occasion to brush up and overhaul your knowledge.

The second part (Chapters 4, 5 and 6), is the one that struck me most for the depth of provided information and the richness of though. Rather than throwing at the reader usage dictates on one or another regex flavour, the author explains with a wealth of details the inward mechanisms which make regexes run and how you can exploit such knowledge to write better expressions.

Chapter 4 presents the different families of regex processing engines (namely, DFA, traditional and POSIX NFA), whose internal behavior differs so greatly that writing a regex in the appropriate way can make a substantial difference in both efficacy and efficiency. If you thought you knew it all about greedy and lazy regex operators, possessive quantifiers, backreferences and lookaround, you'd better think again: I was pleasantly surprised to discover how ignorant I was (to be honest, I had never heard of lookaround operators before!).

Chapter 5 slows down a little bit to let the reader absorb the massive previous chapter. Some simple (but still tricky) examples are presented, showing how to apply the techniques explained up to this point. A couple of examples are perhaps too contrived (ever needed to match aligned groups of 5 digits in an unspaced stream of characters?), but it is instructive anyway to follow the reasoning behind the construction of a complex regex.

Chapter 6 focuses on efficiency, considering how backtracking and matching can drive your regex engine to exponential complexities. Optimization techniques are then presented, first by explaining the automatic optimizations performed by the most common regex engines and then by giving a practical list of hints that you can follow to be sure that your expression will run as fast as possible. Again, I was quite surprised to find out how small changes in a regex can make such a big difference to the engine (and give rise to noticeable performance penalties if ignored).

What I absolutely liked most was that the author explains exactly why a certain optimization works, based on the information given in Chapter 4 (and provided that you have been able to assimilate it in the first pass). Finally, a paragraph entitled "Unrolling the loop" really put me in a good mood, reminding me of the past times of "old school" asm programming.

The third part of the book devotes three chapters to PERL, Java and .NET, respectively. Each chapter goes through the syntax and features of regexes for each language: while the information provided on Java and (VB).NET is quite commonplace, in the case of PERL the author deals with aspects rarely covered elsewhere, like dynamic regexes, embedded-code constructs, regex-literal overloading and specific optimization techniques.

What's to like In one word: insight. The author is definitely knowledgeable of regular expressions and the whole book is filled with thoughtful suggestions and hints. Still, a friendly and straightforward writing style makes reading pleasant and seldom boring (well, you wanted details, didn't you?) while you learn internal regex mechanics rarely available elsewhere.

A further nice point is the broad view offered to the reader, starting from regexes in general and focusing on specific flavours only in the final part of the book. The second edition also offers up-to-date information, covering the .NET framework and the latest versions of PERL (5.8) and Java (1.4).

What's to consider Despite the book's reassuring conversational tone, dealing with such a specific topic with so many in-depth details might sometimes become boring, especially if you do not have a strong interest in getting the most out of regular expressions or in knowing how they internally work. If you are just an occasional regex user and dwell in manual pages, you can probably live without this book. Also, it is a pity that specific sections on Tcl, emacs and awk have disappeared in the second edition (maybe they were not as current as the .NET framework ?) and that pcre (a C regex library) is barely mentioned. The summary Regular expressions are tied so strongly to the *nix culture that everyone who has been exposed to that culture has come to use them in a more or less conscious way. Still, most of the documentation around lags on basic features and presents only the most common regex operators. Mastering Regular Expressions is the book to read if you want to go further and get serious about regexes: even if extreme optimization might not be a big concern today, understanding how regex engines work under the hood greatly helps also in creating everyday small expressions. Table of Contents Preface
Chapter 1. Introduction to Regular Expressions
Chapter 2. Extended Introductory Examples
Chapter 3. Overview of Regular Expression Features and Flavors
Chapter 4. The Mechanics of Expression Processing
Chapter 5. Practical regex techniques
Chapter 6. Crafting a Regular Expression
Chapter 7. Perl
Chapter 8. Java
Chapter 9. .NET

You can purchase the Mastering Regular Expressions, 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.

emmastory writes "Mac OS X Unleashed is not a pocket guide. It's more of a massive tome than anything else - at over 1500 pages, it's probably the heaviest technical book I own. (And that's including Deitel & Deitel's C: How to Program.) Since Mac OS X Unleashed describes itself as 'a complete guide and reference for Mac OS users,' my biggest question when approaching the book was whether this is in fact the case. It seems like if you're going to shell out for an OS X book of this size and price, then it should ideally be the only OS X book you'll have to buy." Mac OS X Unleashed (2nd Edition) author John Ray, William C. Ray pages 1560 publisher Sams rating 7/10 reviewer Emma Story ISBN 0672324652 summary A massive book that aims to be a complete OS X reference

What I Liked
There's no shortage of good things about Unleashed, but the best is probably that the authors assume, for the most part,that you already know how to use your computer. Although there are many good books out there for those new to Macs, this is not one of them and does not try to be. That means that if you've already achieved a basic working knowledge of Mac OS, there's still well over a thousand pages of information intended especially for you. A line from another review of Unleashed (posted anonymously on Amazon) that rang particularly true after reading the book: "If you're looking for a book that says 'this is called a mouse' and tells you where to find iTunes in order to click on it, or drops the bombshell that command-p will print in many applications, you don't need this volume, but if you want to get your hands dirty, it's an excellent resource."

However, I can understand that many people do want the basics in an OS X book. In fact, another Amazon reviewer makes this very point: "Coverage of the iApps is far less than it should be, and there isn't enough information for a novice user like myself. I thought the author spent far too much time on the UNIX and Terminal side of Jaguar and not enough on the real-world tips that I've found in other books." Still, I personally don't really see that as a problem. There are plenty of real-world tips as long as your real world involves a shell, and if there's one thing I've never needed a book for, it's the iApps. In fact, I've always found it irritating that other OS X books spend so much time on them. But that's me, and I'm not everyone.

There were several sections of the book that surprised me, including the chapter on web programming. It makes sense, though - the book is intended to "unleash" OS X, after all, and OS X does come with an Apache installation (even if System Preferences calls it Personal Web Sharing). Given that every OS X box has a webserver, it makes sense that many OS X users would want to know more about related topics. In fact, the chapters that focus on system and network administration comprise a pretty thorough introduction to the BSD side of OS X, and were fairly impressive. These were my favorite sections of the book, probably because they're topics rarely dealt with - or at least rarely dealt with well - in Mac books.

What I Didn't Like
The book suffers from some minor issues typical of most massive technical volumes - it's informative, but also dry, dense, and not terribly readable. Also, while I appreciate the depth and scope of the book, it is a little unwieldy. This isn't something you'll be reading in bed or on the subway. It's not a cheap book, either - its list price is $50. These problems are neither hugely important nor terribly surprising, but they're also not inevitable - reference texts can be thorough without being dull, it's just that this one happens to be both.

Probably the only other real complaint I have with the book is that at times it seems as though it can't decide who its audience is. As I mentioned above, one of the things I liked about Unleashed was that most of the book seems firmly aimed at the intermediate to experienced user. And yet if that's the case, then the chapters that cover things like Desktop Accessories (Calculator, Clock, Key Caps) seem out of place. It doesn't seem like the introductory material offered in the book would really be enough to serve as a tutorial for an absolute beginner (as evidenced by complaints like the one I quoted earlier), but at the same time it's difficult to figure out who else would need it. However, I'm not suggesting they skimped on advanced topics to squeeze in inappropriate Clock coverage - if there's one thing this book has, it's plenty of everything.

The Bottom line
I believe that Unleashed does live up to its title, and does a good job in the process. It's not an introduction to OS X - it's about getting more out of your system after you've already learned the basics. It doesn't (usually) try to be a beginner's book, but a quick-learning novice would probably do fine with it, and any moderately experienced Mac user will probably find that it serves his or her purposes effectively and efficiently. If given the choice (and funding), I'd probably still go with a couple different books, but I think Unleashed has in fact reached its goal of being a complete guide to OS X. You could do just fine with only this book, and at $50 it may be cheaper than buying a couple smaller books separately.

And Furthermore
Other reviews and sources of information on the book:

• Review at macosxhints (from whence another Mac book, incidentally)
• Review at osnews.com
• Review at mymac.com
• Epinions page for the book, which as it turns out isn't all that useful
• Amazon's page for the book, including many customer reviews

You can purchase the Mac OS X Unleashed from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

danny writes "Friends have been recommending Ken MacLeod's science fiction to me for some time, and I've finally read The Cassini Division. Read on for my review - and check out my other science fiction reviews." Nothing says the start of summer like some paperback science fiction. The Cassini Division author Ken MacLeod pages 240 publisher Orbit rating 7 reviewer Danny Yee ISBN 1857237307 summary politics in the 24th century

At the beginning of the 24th century, the inner Solar System is dominated by the socialist Solar Union. Their front-line fighting force, the Cassini Division, defends against viral attacks from post-human Jovians and keeps careful watch on a wormhole. Ellen May Ngwethu, a member of the Division's Central Committee, travels to areas of Earth occupied by "non-cos", low-tech anarchists who still use such antiquated devices as money. Her goal is to find the physicist Malley, whose help is necessary to find a way through the wormhole. And after taking the losing side in a debate over whether to bomb the Jovians or to try to communicate with them, Ellen travels through the wormhole to ultra-capitalist New Mars.

After a slower opening, there largely to link back to earlier books set in the same universe, The Cassini Division rattles along at a good pace. It is not particularly compelling as a novel, however, with no characters that really come to life. Ellen has centre-stage throughout but remains something of a cipher, her dominant feature her dedication to "the true knowledge" on which the Solar Union was founded ("self interest") and her hostility to non-humans, both rooted in her personal history. And none of the other characters gets much play at all. Suze, for example, is a sociologist who joins Ellen early on in the story and has as high a profile in it as anyone else, but she could still have been trivially edited out.

The science is "space opera" style, deployed when necessary for the plot but otherwise passed over, and the intellectual interest comes from the politics. This takes the form of open discussions of political theory and depictions of different forms of social organisation in action, but it never becomes didactic or stodgy. MacLeod himself is a Trotskyist libertarian, a label which gives some feel for his eclecticism, and he depicts very different political systems working reasonably well -- though he often verges on parody. There are also plenty of little jokes, such as a statue of Mises in the Central Planning Committee building.

A significant factor is that aging has been stopped, so many people are centuries old and have political views formed in the 21st century. This makes the recurrence of current political ideologies three centuries down the road more plausible, but it is also a key stabilising factor. Whether in non-co areas of Earth, in the Solar Union, or on New Mars, to a great extent the system works because it's what people are accustomed to. And even the Jovian "fast folk", descendants of humans who moved into computers and experienced a kind of singularity, have some continuity with their past.

Overall? There's not much more to it, but The Cassini Division makes a decently entertaining action story, with plenty of ideas for anyone interested in political theory. I'm not going to rush off and buy Ken MacLeod's other books, but I'll keep an eye out for a chance to borrow them or scam review copies.

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

SPK writes "A colleague and I recently discussed how New Riders's most highly regarded book -- Paul DuBois's MySQL -- corresponds to O'Reilly's worst dud: MySQL & mSQL. Charles Bookman's Linux Clustering does nothing to improve New Riders's reputation. The book is divided into eleven chapters, unevenly distributed among three sections: an overview of clustering for Linux, building clusters, and maintaining clusters. Four appendices provide brief information about online clustering resources, options for RedHat's 'Kickstart,' options for DHCP, and information on 'Condor ClassAd Machine Attributes.'" To find out why Krause was so displeased with this book, read on below for his review. Linux Clustering. Building and Maintaining Linux Clusters author Charles Bookman pages xv + 265 publisher New Riders rating 2/10 reviewer Steve Krause ISBN 1578702747 summary A guide to clustering software, networking, and journaling filesystems

Bookman emphasizes a central piece of wisdom that no system administrator should ignore: redundancy. In the case of high availability clusters, parts redundancy is the name of the game, but one should not forget the human component; no administrator should be caught with only a cell phone -- keep a pager just in case. However, in a post-modern turn that might seem brilliant if it were applied in a work of fiction rather than a technical book, the author seems to apply the concept of redundancy to the text itself.

That the book began not as a book but rather as a collection of talks or presentations, or some other smaller format, is evidenced by the repetition of information between chapters and sections. Such nearly poetic repetitions also occurs within sentences and paragraphs (e.g. "nightly backups each night" on page 25).

An editor never looked at Linux Clustering; the book had two "technical reviewers" but their contributions seemingly didn't include fixing mangled syntax and strained style. On page 14 in the second paragraph a large segment of a sentence from the previous page is pasted into another sentence, resulting in a nonsensical block of text. The number of hyphenation, syntax, word choice, and subject-verb agreement errors is atrocious and makes the book difficult to read.

Some of the misinformation in the text appears to be unintentional (but ignorance is no excuse for a UNIX systems administrator); some is due to the fact that the author deals only with old (2.2) kernels (though the book came out 18 months after the 2.4 kernel release), old versions of journaling filesystems, and old distributions; and yet other misinformation is the result of misplaced attempts at humor (such as stating that GNU stands for the Gateway Naming Utility; one can only hope that this was intended to be funny). Other jokes often misfire, but do point to the intended audience (consider, for example, the section heading "Space: The Final Frontier").

In the Introduction, the author indicates that the book should be read by "Linux enthusiasts and users who want to get a Linux cluster up and running with the least amount of fuss." The organization of the book will not, however, aid this enterprise, for there is little "how to" information provided, but rather a great deal of background information on compiling kernels, various types of journaling file systems, and RedHat's Kickstart (perhaps inappropriate considering that the book specifically states that basic information will not be covered). Another section or two deal with basic networking and security. Various types of clusters are discussed, as are a few of the types of clustering software (e.g. Condor and Mosix) available.

The book, however, is clearly intended for administrators of clustering systems; a special emphasis is high-availability and load-balancing clusters. Parallel computing and the types of applications end users would wish to run receive far too little discussion.

Almost all technical books regurgitate the contents of freely available FAQs and HOWTOs to some degree, yet the good ones summarize the relevant points, make dry documentation more accessible, and give the reader some new insights. Because Bookman's Linux Clustering suffers from heinous spelling, grammar, and style errors; deals primarily with outdated software; contributes little new to the discussion; and doesn't speak to non-admins, I can only recommend that those interested in Linux clustering stick to online FAQs and HOWTOs.

You can purchase the Linux Clustering: Building and Maintaining Linux Clusters from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

honestpuck writes "Many years ago I learnt my AppleScript skills from a book by a gentleman by the name of Danny Goodman and I was happy to find him tackling the subject of dynamic HTML in "Dynamic HTML: The Definitive Reference". Indeed this is the second edition and seems supremely up to date." Read on for the rest of honestpuck's review. Dynamic HTML: The Definitive Reference (2nd Ed.) author Danny Goodman pages 1343 publisher O'Reilly rating 9 reviewer Tony Williams ISBN 0596003161 summary Truly definitive reference for a huge topic

Goodman has tackled a complex subject. With changing standards and even quicker changing browser compatibility it can be a nightmare trying to get a dynamic web site working across disparate browsers and operating systems. A guide that tells you exact syntax and exact compatibility can be invaluable, but is only as good as the research behind it, an area where I cannot fault Goodman.

This volume covers XHTML, CSS and DOM with a large smidgeon of JavaScript. It's not an easy book to get into and consume in large chunks as it does little hand holding but as I was prepared to knuckle down and work at the topics (with much help from various web sites such as CSS Zen Garden) I found it perfect for me. Goodman has recently released JavaScript & DHTML Cookbook which I have found to be a marvelous volume to assist the process of understanding these technologies, though I am still looking for a good, up to date tutorial on CSS (recommendations welcome).

The target audience would be best summed up as those who have done a fair amount of HTML hand coding and some work in dynamic HTML. The book also adds that you should have "the basics of client-side scripting in JavaScript" and I would agree, when I first acquired this book my JavaScript skills were exceptionally primitive (mainly at the 'plug in example' stage) and found the latter sections of this book heavy going and not much help; now that I am a better JavaScript programmer I find these parts much easier to understand and use.

The book is divided into four parts, 'Applying Dynamic HTML,' 'Dynamic HTML Reference,' 'Cross References,' and 'Appendixes'. I found the first part particularly helpful when converting my old site across to a more dynamic CSS-based site as it helps with various strategies for making sure your content works across browsers and various methods for making sure that visitors with older browsers and search engines can still retrieve valid pages. Goodman's approach of increasing complexity through this part also suited a movement from a straight HTML site to one using XHTML and CSS. This is also where Goodman's writing can shine: it's an excellent guide to all the technologies and acronym soup. The appendices are marvelous, from 'A,' a list of colour names with their RGB value, through a list of character entities to a 50-page list of all HTML tags, their attributes and if they are supported in the two HTML 4 and three XHTML 1 standards.

The reference parts are well structured with extensive notes on browser support and which particular standard (DOM 1, DOM 2, CSS 1, CSS 2, or none) the tag or attribute comes from. For example, in the DOM section the reference gives you the object name, which versions of Navigator and Explorer support it, the DOM version (if any), a short explanation, then an object reference example, list of properties, methods and event handlers. For each of the properties it gives an example, the type and if it is read-only or read/write. For methods it gives the return value and parameters. This sort of attention to fine detail is taken throughout the book. You end up with a book 1343 pages long and a 51 page index. Goodman mentions in his preface that the book now encompasses 'more than 15,000 unique instances of properties, methods and event handlers,' a figure I'd believe.

O'Reilly have their usual page for this book that includes a sample chapter in PDF, the Index, Table of Contents and an Errata page. There are few Errata and only one in the code examples. Speaking of examples, you can download the complete set of code examples from the book.

There is also a page at O'Reilly for the author, Danny Goodman with links to some excellent articles and book excerpts on dynamic HTML and JavaScript.

I found this a hard book to review, as are most references. The questions I asked were: one, Does the book cover all the material?; two, Is it correct?; three, Is it easy to find the entry you want? and four, Are the entries laid out in an easy to understand manner? In these criteria this volume rates well, with the added bonus of some good material in the first section for understanding the nuances of dynamic HTML in a multiple browser, multiple operating system world.

If you are doing a lot of work in dynamic HTML then this book is probably an essential. While I don't consult it every time I start working on HTML when I run into trouble it is the first place I turn to make sure my syntax and browser compatibility are straight. This book ain't cheap, and it ain't small but I'd recommend it for your desk if you're working with web sites.

You can purchase the Dynamic HTML: The Definitive Reference (2nd Ed.) from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

If maintaining the security of networked machines running Microsoft Windows is part of your job (but you need a touch of Oracle and UNIX advice, too), take heart. elwing writes "Don't let the cover title and camo look turn you away -- Special Ops is a no-nonsense guide to securing your network from inside attackers. This is one of the first books I've seen which covers this topic in detail. It doesn't skimp on external threats, but the majority of the book deals with host based security." Read on for the rest of elwing's review. Special Ops: Host and Network Security for Microsoft, UNIX, and Oracle author Erik Pace Birkholz, et al. pages 1040 publisher Syngress rating 8 - Worth Reading reviewer elwing ISBN 1931836698 summary Taking a look at securing your network from the inside.

In order to get the most out of Special Ops, I suggest that you brush up on your system administration skills, particularly Microsoft technologies. The book is aimed primarily at security and systems administrators, but several of the chapters are either aimed specifically at management (Chaps 17 & 18), or could easily be understood by them (chaps 1-3).

The authors write in a conversational, matter-of-fact style, including personal anecdotes and experiences where appropriate. The editors did a great job of "smoothing out" the styles of the different authors to give Special Ops a consistent feel.

One of the best features of Special Ops is the end-of-chapter content. These summaries include a "Security Checklist" which creates a nice list for admins to take into the field, a one-page summary of the chapter, links to relevant web pages, relevant mailing lists, other books to read for more in-depth information, a "Solutions Fast Track," and a FAQ. Some chapters list all of the freeware and commercial tools used/mentioned in that chapter. The Solutions Fast Track is a great section to hand to your slightly more technical manager explaining why you should secure a specific service. These chapter extras make Special Ops a great reference book, even if you never bother to read the rest of it.

Another great feature is the "Notes from the Underground ..." sections scattered throughout the book. All of the authors have worked in security for several years, and they share specific examples of attacks or other interesting tidbits they've seen over the years.

I had trouble giving Special Ops a rating of 9 or 10 for a few reasons. Even though the book is an easy read, it's a lot of information to digest. The subtitle makes it sound as if Microsoft, UNIX, and Oracle would receive equal treatment: not so. While there are 7 chapters on Microsoft specific technologies, UNIX and Oracle rate one chapter each. I would have preferred to see Special Ops split into 2 or 3 books, giving equal attention to all of the technologies.

The authors' bias towards certain commercial tools shows through as well. Granted, the majority of the authors are also Foundstone employees, but they should have given equal treatment to all tools. Explain the strengths and weaknesses of each tool and allow the reader to decide on the "best" tool.

All in all, Special Ops is a great book. It will definitely reside on my reference shelf for years to come.

Table of Contents

1. Assessing Internal Network Security
2. Inventory and Exposure of Corporate Assets
3. Hunting for High Severity Vulnerabilities (HSV)
4. Attacking and Defending Windows XP Professional
5. Attacking and Defending Windows 2000
6. Securing Active Directory
7. Securing Exchange and Outlook Web Access
8. Attacking and Defending DNS
9. Attacking and Defending Microsoft Terminal Services
10. Securing IIS
11. Hacking Custom Web Applications
12. Attacking and Defending Microsoft SQL Server
13. Attacking and Defending Oracle
14. Attacking and Defending Unix
15. Wireless LANs: Discovery and Defense
16. Network Architecture
17. Architecting the Human Factor
18. Creating Effective Corporate Security Policies

You can purchase the Special Ops 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 writes "I read this book to improve my knowledge of Linux networking, and in that regard it was a huge success! It was also an enjoyable and easy-to-read book. I am pretty much a Linux beginner, and know 'enough to be dangerous.' My existing home LAN consists of 5 machines: one running Mandrake Linux 9.1, one RedHat 9 (laptop), two Windows XP, and one Windows 98. These are connected to a commercial (Siemens Speedstream) router/switch and share internet access via a cable modem. All the computers can communicate with each other and share files, using Samba. The router also functions as a print-server for a laser printer, which the Linux machines print to via CUPS." Whether your network is bigger, smaller, or hypothetical, Dan's review (below) suggests that O'Reilly's Linux Network Administrator's Guide, 2nd Edition would be useful to have at hand as you build or troubleshoot. Read on for the rest. Linux Network Administrator's Guide, 2nd Edition author Olaf Kirch & Terry Dawson pages 475 publisher O'Reilly rating 8/10 reviewer Dan Clough ISBN 1565924002 summary How to get your machines talking amongst themselves.

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 ;)

HeavyJay writes "When I purchased QBASIC Programming for Dummies, I expected a clear, concise tutorial on how to construct programs in QBASIC. I'm new to the world of programming, and, having had luck with the Dummies series before, thought this the best place to start off. How very wrong I was." Read on for more; readers with recommendations for better (newer?) QBASIC books are encouraged to contribute. QBASIC Programming for Dummies author Douglas Hergert pages 399 publisher IDG Books Worldwide, Inc rating 5 out of 10 reviewer HeavyJay ISBN 1568840934 summary "The Fun and Easy Way to Learn QBasic Programming."

I've read countless books and online tutorials on QBASIC, C++, PHP, and other various languages. I'm sure all you wise programmers can tell me the first sample program that comes to mind with any language, can't you? The classic 'Hello, world!' example. This easy app starts off would-be programmers with a level of confidence and understanding. To my surprise, Douglas Hergert decided not to use the ever-popular example program. So, you might be wondering, what did he use in it's place? A four-page-long currency converter.

This was Mistake #1.

The book started off making me feel stupider than I actually am. This oftentimes discourages readers from pursuing, and the book takes to the shelf, perhaps never to be picked up again. I've noticed that the best way to capture a reader's attention (and explain the most) is to start off with PRINT, INPUT, IF...THEN and GOTO. Then move on to loops, and get technical from there. It best prepares the reader for everything in store, rather than making them feel like idiots. The book didn't do this at all. It started off making in such a way that anyone without experience would be completely lost. IF...THEN doesn't even come in until the eleventh chapter, despite being one of the most important tools in the language!

So, what good can I say about the book? Not much, except that it came with some practical applications. This brings up another grievance I have with it, that being the lack of an accompanying disc. I feel every book on programming with long examples ought to come with a disc containing all example programs, so that the reader can tweak and observe them as he sees fit, without typing in five pages of code. The best way to learn is often by example, and discouraging lazy people doesn't help the learning process along.

Alas, the book does contain some humour, as it's other brothers and sisters from IDG often do. With chapter titles such as Text, Lies, and Videotape and How to Manage Arguments and Influence People, a book can't be completely bad.

Although I suggest beginners steer clear of this book, it can be useful to experienced programmers (supposing they don't think QBASIC a waste of time). It goes deeply into data structures, arrays, and databases. There are many helpful features, but it's definitely not a book to learn from.

You can purchase the QBASIC Programming for Dummies from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Priscilla Oppenheimer writes "Annlee A. Hines' book Planning for Survivable Networks, is quite a page-turner. Yes, that's surprising for a technical book, but I found it to be true. I was fascinated by the stories of real companies (Lehman Brothers, the Wall Street Journal, and others) that survived the 9/11 attack and resumed business quickly. There are also stories from other disasters, both man-made and natural, and information on companies that were not able to quickly resume business. The author summarizes the stories with explanations of what went right and what went wrong, with advice on developing your own disaster recovery plan." Read on for the rest of her review. Planning for Survivable Networks author Annlee A. Hines pages 320 publisher Wiley Publishing, Inc. rating 10 reviewer Priscilla Oppenheimer ISBN 047123284X summary Designing networks that can recover from natural and unnatural disasters
As Hines explains, Lehman Brothers had headquarters in Tower 1, as well as in 1,2,3 World Financial Center (across the street from the WTC towers). Lehman moved to a backup recovery location and performed cash-management functions the same day as the attack. The company was online trading fixed-income securities by the next day. They had 400 traders online when the NYSE reopened Monday, 9/17.

The Wall Street Journal (WSJ) published the story of its own recovery and Hines used that as source material for her book. WSJ had an extensive disaster recovery plan, based on lessons learned in the 1990 power blackouts in New York. After the blackouts and a subsequent fire in the emergency generator room, WSJ decided that it would never again depend on just one location being operational. WSJ opened other offices that could perform some of the necessary tasks to bring out a paper. Geographical diversity of resources seems to be a key to success.

When the 9/11 terrorists attacked the buildings across the street from WSJ's main offices, senior managers called for an evacuation, knowing that they could still produce the paper. The Wall Street Journal managed to publish a full newspaper with eyewitness accounts of the tragedy the next day.

Hines' writing is easy to follow. Although she delves into some technical details, with the requisite IP and TCP header depictions that you will find in so many networking books, the book can easily be read by managers and business people. Planning for Survivable Networks has many factual tidbits about disasters of all sorts, and although these are interesting, the primary benefit of reading the book is to gain an understanding of the characteristics of companies that sustained business after a disaster compared to companies that did not.

As Hines says, the companies that survived disasters all had disaster recovery plans in place. The plans were activated by decisive managers, who also promptly got their people out of harm's way. (If people don't survive, it won't matter much if systems survive.) Another point she makes is that the managers had to be adaptable. Not everything went according to plan, and it shouldn't be expected that it will.

The book opens with the author being rocked by a terrorist-caused explosion herself. She wasn't present for the 9/11 attackers. Rather, the bombing she survived occurred at Ramstein Air Base in Germany, 20 years before. A retired Air Force officer, she has dealt with threats all over the world for many years. Her direct command and control experience has taught her many lesson, which she shares with the reader in Planning for Survivable Networks.

Probably one of the most useful chapters, Chapter 11, "The Business Case," offers advice on presenting to management a case for a network continuity plan. According to the back cover, Hines has taught economics at a community college, and I would say that experience helped her explain the many costs involved in having a disaster recovery plan, including fixed, variable, direct, and indirect costs. She also explains the expected value of having a plan and how to sell that to management.

I recommend this book as an informative discussion of how companies can ensure business and technology continuity in a world with hackers, terrorists, natural disasters, and human error. It's a practical book, but also a surprisingly uplifting book, considering its technical content. I truly enjoyed reading about the adaptable human spirit that enabled managers and workers to keep their businesses going after the 9/11 attacks.

You can purchase the Planning for Survivable Networks from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

rjnagle writes "I got my cubicle colleague interested in OpenOffice.org when I said, "Here's something that can convert your Word files to PDF ... for free!" By now people hip to the open source concept use OpenOffice.org for everyday applications, yet MS Office is still the predominant application in the home and workplace. Many educated people have still not heard of it. Why?" Read on for Nagle's four-part answer to that question, and his (lengthy) review of Michael Koch's Special Edition Using Star Office 6.0 -- the content applies to StarOffice's free cousin OpenOffice.org as well. Special Edition Using Star Office 6.0 author Michael Koch pages 1078 + index publisher Que rating quality: 5 stars; usability: 4 stars; weight: 1 star reviewer Robert Nagle ISBN 0789728338 summary Great for easing the transition to Openoffice/Staroffice.

First, PC makers rarely have financial inducements to preinstall open source applications, especially when it eats into their upsell margins. Second, people have a misconception that documents produced in MS Office can only be read by MS Office (a fact which leads Richard Stallman to call for an end to all Microsoft Word attachments ). Third, subsidized prices and the wide availability of instructional material ensure that teachers use these commercial products for class and give assignments requiring them. Finally, consumers switching to an open source product need confidence that the open source application has equivalent functionality and adequate documentation to reduce the learning curve.

Fortunately, a first-class user guide on OpenOffice.org/StarOffice has been written, and that book is Michael Koch's Special Edition Using StarOffice 6.0. This book, actually a second edition, covers the new version and gives fuller treatment to StarOffice writer and the HTML editor. Despite the use of "StarOffice" in the title, this book actually covers both StarOffice and OpenOffice.org in depth.

An an aside, let me compliment Que editions for the legibility and usability of layout. (Que also produced the excellent Ed Bott's Special Edition Using Microsoft Office XP). Nice readable texts, lots of boxes, tips and cautions. Every chapter finishes with a helpful troubleshooting section.

Two immediate reactions: 1) Gosh, I didn't know OpenOffice/StarOffice could do all that! I was pleasantly surprised, for example, to learn the number of graphic capabilities the program has. 2) This book covers functionality in considerable depth, with enough content to satisfy the newbie as well as the advanced user. In addition to documenting the office software, the book also includes reference sections on StarOffice Basic, using data sources, building forms and macros. It also includes a chapter on Adabas, the database that comes as part of the StarOffice package (but not with OpenOffice.org).

Koch benefits from the fact that users already start with a good conceptual framework of what MS Office products are supposed to do. The biggest conceptual challenge in moving from MS Office to Star/OpenOffice is getting used to the idea of applying styles to text instead of just clicking on an icon for formatting. MS Office actually has terrific styling capabilities (and a usable interface for managing styles),but Microsoft's friendly GUI discourages users from thinking about document structure. Contrast that to OpenOffice.org, which nudges the user more firmly towards styles. Managing the different layers of styles in OpenOffice.org can be tricky and confusing, so Koch spends a considerable amount of time and space on that. Another chapter on sharing and exchanging information with MS Office users goes into exquisite detail about compatibility and formatting losses when converting documents, as well as the StarOffice XML file format.

Cordelia of Buffy the Vampire Slayer once said, "There are books about computers? Isn't that the point of computers, to replace books?" Perhaps I am just cheap, but when evaluating a user guide, I often ask whether the online help isn't good enough. Or whether newgroups/websites/forums are adequate. Or whether the user interface is intuitive or allows you to discover a solution by just playing around. Dozens of heavy thousand-page books clutter my apartment, leading me to wonder whether the convenience of a gigantic dead-tree reference guide outweighs the increase in clutter. Every time I move to another apartment, I keep lugging those gigantic SQL and C++ books I haven't consulted for years, but feel compelled to keep around. (Contrast that with the very portable and handy Oreilly's Linux Server Hacks: 100 Industrial-Strength Tips and Tools, (reviewed on Slashdot), which covers most sysadmin tasks AND can be stashed in a backpack without causing whiplash).

For the last two months (in which I used OpenOffice.org thoroughly), I performed a little experiment. Where was the best place to find answers to my OpenOffice.org questions? I tried consulting the online help, then the book, then the newsgroups and openoffice websites. Here are the results:

1. Adding page numbers. The book had the best information, though what do you look under in the index? I eventually found it under "Numbers, Writer" (?!). Online help was useless. (The answer is to insert a footer and then insert a page number field in the footer).
2. I just created a hyperlink in the HTML editor. But the underlined style is bleeding to the text after the link. How do I stop that? Neither the book nor online help provided the answer, although the newsgroup did after 24 hours. (The answer is to press the End key or to select Format >> Default)
3. How do I create an HTML style with the stylist which specifies the background color of a table cell? (No answer from anywhere, although Koch admits that that the StarOffice HTML editor is "temperamental").
4. While drawing a flowchart on the Draw program, how do I save the entire image as a jpeg and not just the highlighted part? (By grouping the components together, the book helpfully advises. The online help offers nothing).
5. On a spreadsheet, what is the keyboard shortcut for bringing the cursor back to the left column? (Keyboard shortcuts are easy to find in the book. Couldn't find it in the online help).

Generally, the book had the most reliable and in-depth information. That was especially helpful when trying to perform a complex action (like creating a table of contents). But the majority of my inquiries had to do with using the interface, not functionality. Often the sheer size of the book made daunting the simple task of finding a function on a dialog or a keyboard shortcut.

That is the paradox of super-sized application manuals. Surely one doesn't read them from cover to cover. But after an application reaches a certain level of complexity, the software interface is no longer intuitive, and you pretty much need a book just to find things in the interface. As one who does technical writing, it may sound funny to say, but often my favorite thing about these super-size manuals are the screenshots. I can't tell you how many times I've browsed through a book and come across a dialog box I never knew existed. On the other hand, when application manuals reach a certain size, navigating through "book interfaces" becomes almost as difficult as navigating through the software interface or help system.

Online help is good when you know what you're looking for (i.e., when you have a specific search term to look for). Books are good when you don't know what you're looking for. With books, the reader can flip through pages in the general vicinity of a topic and randomly stumble upon the right information. Books allow the user to bypass the outlined hierarchy of online help and learn the appropriate terminology for describing the task (which then makes it easier to find things in the online help).

A recent visit to a technical bookstore and a large chain bookstores showed no books on the shelf for StarOffice, but dozens of books on Microsoft Office, That is too bad, because Using StarOffice 6.0 provides much-needed in-depth coverage on an application whose user base will grow as tight budgets cause companies and public sector agencies to examine open source alternatives.

* PDF conversion (as well as docbook and Flash) export are available on the OpenOffice.org 1.1 Beta 2 build.

Other OpenOffice.org Resources:

Kaaredyret has the best English language OpenOffice links page . ooodocs.org has a lively Forum for OO users. Or if you want, you can look at a PDF of the official Staroffice Documentation (400 pages)

ROBERT NAGLE (aka idiotprogrammer )is a technical writer, trainer who doesn't think that open source documentation sucks . He works for Texas Instruments in Houston, Texas. You can purchase the Special Edition Using StarOffice 6.0 from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

emmastory writes "Mac OS X Hints is a brand-spanking new O'Reilly book containing over five hundred 'power tips' and tricks for (amazingly enough) Mac OS X. The tips are culled from the website of the same name, written and maintained by Rob Griffiths. The book is edited by David Pogue, of Missing Manual and Pogue Press fame. It's 461 pages, list price is $24.95, and the O'Reilly catalog page (containing samples from the book) is right here." Read on for emmastory's review. Mac OS X Hints author Rob Griffiths pages 461 publisher O'Reilly/Pogue Press rating 8 reviewer Emma Story ISBN 0596004516 summary The perfect sequel to the Missing Manual, this book contains 500 tips for OS X

Addressing the Obvious

The most immediate question I had when I heard that O'Reilly would be publishing a book containing hints from macosxhints.com was, of course, Why I should get the book when the hints are already on the site for free? Both the author and the publisher also thought of this, understandably enough. Here's how Rob Griffiths answered the question in a post on the site, when the book was first announced: "The book isn't just a 'cut and paste' job from the site-to-print form. Every hint was rewritten and retested from scratch, and hundreds of screenshots were added to help clarify and explain the hints. In addition, many of the scripts and programs posted here are included (the author of each program was contacted for approval to include their original work in the book -- thanks to each of you for agreeing!)."

The response included in the O'Reilly press release for the book is along the same lines: "'The 500-plus hints in this book are based on tips published in the Mac OS X Hints web site,' explains Griffiths. 'But it's not just a rehash of what's there. Every hint has been rewritten, expanded, organized, indexed, tested for compatibility with the latest version of Mac OS X 10.2, and in many cases, illustrated, making the book an even better resource than the web site."

So the question then becomes: is this really the case? Are the differences between the hints as posted on the site and as printed in the book really significant enough to merit shelling out $24.95?

The short answer is that, in my opinion, the book is worth its price. The long answer is (predictably) a little more complicated. There are, of course, people who are more than willing to do the extra digging on the web to get the relevant content for free -- they'd rather do without the little perks (increased readability, revision, testing, screenshots) than spend potential beer money for a glossy O'Reilly book. And that's fine -- I'm more than sympathetic with this position, being frequently hard up for beer money, myself. But of course there are also people for whom the convenience is just as important as the cost, and who consider the price of the book well worth it in terms of the time saved. If you fall into the former category, don't bother buying the book -- but then, you weren't going to buy it anyway, were you? As for the latter group, rest assured that your investment will not, in this case, be wasted.

What I Liked

I've read several other books on Mac OS X. The one I believe everyone should start with is still David Pogue's Mac OS X: The Missing Manual . If you've already read this book (and enjoyed it) or didn't read it but are confident you've already got the equivalent experience, then Mac OS X Hints is a good next step.

Griffiths assumes you're comfortable using OS X for basic tasks: he doesn't tell you how to log in, or what the Dock is. If you're fuzzy on those kind of basics, you're not quite ready for this book (but you're positively crying out for a copy of the Missing Manual). Additionally, he pushes some not-entirely-obvious processes to the introduction, so you don't have to read the same instructions over and over in the meat of the book itself. After all, once you've been told the first time how to view the contents of a package, you're probably all set in that regard. This is one of the aspects of Mac OS X Hints that I found most appealing, actually - Griffiths just explains in the beginning that he's assuming certain things, and then doesn't bother dumbing anything else down.

I've been a fan of macosxhints.com since I first installed OS X, but it seems like Griffiths's style has really improved for the book -- this may be a function of Pogue's role as editor, as the writing in Hints displays the same familiar, comfortable tone while not skimping on depth or details. Like other books Pogue has been involved in, this one is highly readable but not oversimplified.

It seems like the revision process the hints went through during their transition from site to print has been pretty successful, as well -- despite being familiar with the site, there was a great deal of material in the book that I had never seen, even after reading other OS X books. Additionally, the testing involved in the book's creation removes a great deal of the frustration inherent in the site. As much as I like the site, there have been several hints that have mysteriously declined to function on my own system for whatever reason -- but everything I've tried from the book worked without a hitch.

I also enjoyed the fact that this book, like Mac OS X Hacks , is made for sampling. Each article is short and to the point, and while related hints are grouped by chapter, no single tip depends on the reader having already performed one of the others (unless otherwise specified). You don't have to read the book cover to cover -- you can flip around at will without getting lost.

Incidentally, another plus is that 15% of all Griffiths's profits from this book are being donated to the Doernbecher Children's Hospital. That in itself isn't a reason to buy the book, but it's good to know.

What I Didn't Like

If I can be nitpicky for a moment, I was bothered by the frequency of purely typographical errors. Little things like "than" being used instead of "then," or the bottom edge of a line in a sidebar getting cut off. It didn't keep me from enjoying the book, and I'm sure it's the sort of thing that will get corrected in future printings, but this sort of error occurred often enough that I noticed it, anyway.

Another little thing: I wish URLS had been included whenever a third-party shareware program was mentioned. Of course I know I can Google for DragThing and find it immediately -- but if I'm paying for a book, it seems to me that I shouldn't have to.

There is also the fact that this book is undeniably a book, and that limits it in certain respects (at least when compared to the site). The index is comprehensive and useful, but it's just not as useful as the ability to search the entire text of the book. It's also inevitably dated to a certain degree -- new hints posted to the site, even if they're infinitely more fabulous than ones already present in the book, just won't show up in print for a long time to come. Similarly, if a new version of the OS breaks one of the hints, you'll be able to find out somewhere on the web, but it won't be immediately obvious when you're just reading the book. Of course, these are problems shared by all print technical books, and not just Hints.

One final note: there's a lot of overlap between this book and Mac OS X Hacks, although each book has a significant amount of unique content. If you own one, you probably don't need to get the other, but it's difficult to say which I'd buy if I had to choose. Hacks contains only 100 articles, but they're more in-depth and the tasks they cover are often trickier or less obvious. Hints contains over 500 tidbits, but they're much shorter and often deal with things like key commands that allow you to increase your efficiency, and things of that ilk.

The Bottom Line

If you're the sort for whom time is at a higher premium than money -- maybe you're the kind of person who would buy a boxed *nix distribution instead of downloading it -- then I'd say go ahead and get this book. It's well worth its price as long as you understand that what you're paying for is ease of use and reliability, as well as content. If, on the other hand, you're living on Top Ramen for the foreseeable future, you're probably better off sticking with the site. If you do buy it, I think you'll find it will make a happy addition to your bookshelf -- stick it next to the Missing Manual and dip into it whenever you're sitting through an install or reboot.

You can purchase the Mac OS X Hints from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

CEHT writes "Like Tony Williams said in his review on PHP and MySQL Web Development: "PHP and MySQL are probably the most pervasive add-ons to Apache web servers across the web". And I agree with him. PHP is a very powerful scripting language, so developers (not just web developers) can do almost anything with it." Read on to see how well CEHT thinks O'Reilly's PHP Cookbook helps you do that almost everything. PHP Cookbook author David Sklar and Adam Trachtenberg pages 608 publisher O'Reilly rating 9 reviewer Edmond Lau ISBN 1565926811 summary Solutions and examples for PHP programmers.

The approach that the authors use in PHP Cookbook is great. Like most computer books, the authors usually include a summary (in sentence forms) to illustrate what the readers will expect in each chapter. Skalar and Trachtenberg take this even further by including some preliminary (code) examples to explain the general ideas behind each chapters. The examples in the book are self-contained. In most cases, I've found examples to exactly fit my needs -- this makes it one of the better reference books.

Each chapter in the book is divided into multiple sections of Problem / Solution / Discussion with a FAQ style. In each case, a simple description of a problem is followed by a PHP script as the solution. But the meat is actually in the discussions: in-depth details are included here, where the authors also include references, extended ideas, and scripts to inform the readers how much more they can do about the issue.

For example, I was going to add a simple script to my website to parse RSS/RDF files from certain news websites (CNN, Slashdot, ...), and use it as my Mozilla homepage. (Who wouldn't?) This script seems to be simple, but I may make a mistake here and there. As reference, I opened up the book to the section "Parsing XML with SAX." Then I realized the authors already had the script to parse RSS/RDF files in the discussion. Bravo!

For myself, the most useful chapters I found are: Web Basics, Forms, Database Access, and XML. There are also good examples in topics such as security, internationalization, and file processing/management. However, this book does not cover the basics of PHP. If you are a good programmer, you should be able to get away with this using the PHP Manual. A good book to learn PHP is Programming PHP, also by O'Reilly.

Although this book covers a wide range of topics, it does not cover topics like generating PDFs. I would also like to see the authors add one (maybe two) case studies in later editions. That would give the reader a more concrete example of how to combine tricks presented by this book. Other than that, at the price of $39.95 (or $61.95 CAD), this book is a great buy!

Topics

1. Strings
2. Numbers
3. Dates and Times
4. Arrays
5. Variables
6. Functions
7. Classes and Objects
8. Web Basics - available online as example chapter
9. Forms
10. Database Access
11. Web Automation
12. XML
13. Regular Expressions
14. Encryption and Security
15. Graphics
16. Internationalization and Localization
17. Internet Services
18. Files
19. Directories
20. Client-Side PHP
21. PEAR

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

daltonlp writes "Many stories under the "patents" topic on Slashdot are about objectionable patents (Amazon's one-click purchase patent, for instance). These stories typically draw comments full of righteous indignation and jeers about the incompetence of the US patent & trademark office. Don't you wish you could package that sentiment in a handy, bound volume? Maybe with a few more hard facts than you're likely to find on /. ? Well, now you can." Read on for the rest of Dalton's review of Michael Perelman's Steal This Idea. It's not a new book, but it seems more relevant every day. Steal this Idea: Intellectual Property Rights and the Corporate Confiscation of Creativity author Michael Perelman pages 272 publisher Palgrave Macmillan (April 2002) rating Worth Reading reviewer Lloyd Dalton ISBN 0312294085 summary A hard-hitting look at the state of the U.S. patent & trademark system.

Most of the themes and arguments in Steal This Idea will be familiar to anyone who's read a Slashdot thread on patents. Michael Perelman is an economics professor at California State University. In Steal This Idea, he takes the position that patents (and trademarks, to a lesser extent) hurt science and the economy more than they help. He makes a pretty convincing case.

Roughly half the book is devoted to the negative effects of patents on scientific research. Perelman claims that tying research to intellectual property skews the balance of study away from basic research on fundamental problems, and toward short-term research geared toward improving existing products. Several real-world examples are given--many of the most potent come from the world of biological and pharmaceutical research:

Two decades ago, Philip Needleman, then a researcher at Washington University, in St. Louis, and his co-workers postulated the existence of two cyclooxygenase enzymes, COX-1 and COX-2. By 1990, Dr. Needleman, then chief scientific officer at Pharmacia, had guessed that the COX-2 enzyme plays a critical role in inflammation. By 1992, three other groups, including one at Rochester, had confirmed the existence of the enzymes by describing the genes that control their production. Although Rochester won the patent, the competing teams at UCLA and Brigham Young University claim that their work was fundamental.

Whether UCLA, Brigham Young, or Rochester deserved the patent is beside the point. More important is the idea that the granting of a patent on a bodily substance permits the owner to demand royalties from any company that produces a medicine that targets the substance.

Perelman gives historical evidence of IP hampering the development of new technology. His best example is the thicket of radio patents that entangled the baby radio industry, until the U.S. government voided many of them in the interest of accelerating radio technology during WWII.

Finally, Steal this Idea makes the case that scientific progress in the last half of the twentieth century owes a greater debt to basic research from academic and publicly-funded scientists and researchers than to corporate research. The concern is based on the large amount of time (decades, rather than years) needed for basic scientific discoveries to become marketable products is largely ignored by corporate research, which is focused on quarterly results.

It's curious that the internet--maybe the most obvious example of this, is barely mentioned. After all, business research has failed miserably at defining network protocols that match the resilience and utility of the network designed by publicly-funded scientists in the 60s. This may be because Perelman is less interested in obvious examples than lesser known ones, of which there are several in the book.

The second half of the book argues against patents (and Intellectual property in general) in terms of economic theory. Economics is Perelman's area of expertise, but it is not mine. I had to read most of these chapters twice before I understood them. They're interesting stuff, though. Perelman illustrates various ways economists attempt to shoehorn non-tangible goods (information) into economic models based on "lumpy objects." He illustrates the flaws in several of these models, and how these flaws translate into inefficiencies in actual markets.

Good: The book isn't just a rant, although it sometimes reads like one. Perelman is firmly biased against IP, and he sometimes uses a few paragraphs to rail against corporations in general. But the book is logically laid out, and presents evidence in well-defined pieces, always clear about what each example is meant to illustrate.

The examples. Those mentioned above are just a few of the many real-life events noted in Steal this Idea. They comprise the bulk of Perelman's case against patent IP. It's always tough to build an argument on anecdotal evidence, but in this case, there's a great deal of evidence.

The scope. I had doubts that a 211-page book could do justice to the issues with every type of intellectual property. Fortunately, Perelman doesn't attempt to cover copyrights, and barely touches trademarks. The overarching theme of the book is that intellectual property (mainly patents) in the hands of corporations works against the original goals of its creators--to encourage innovation and help the economy. The book does a solid job of supporting this claim.

Bad: IP is supposed to be a "limited" monopoly. Patents are, arguably, the most "limited" of the three types of IP in the US (copyrights, patents and trademarks). Perelman could have acknowledged this, and given concrete examples of why the limits aren't enough to balance the monopoly power. He doesn't explicitly do so.

Copyright is nowhere to be found. That's not all bad, since any book would be hard-pressed to do a better job of handling copyright issues than Jessica Litman's Digital Copyright . Still, Steal this Idea might have included a few more references to copyright-specific cases or works, if only to encourage further reading (patent & trademark examples include many references).

Perelman gives some illustrative figures about why the patent mess is so bad, and why the USPTO is unable to control it. But there's not much meat there. Hopefully, someone will take a more in-depth look at the USPTO itself, and how it operates.

Conclusion: Steal this Idea has a great deal of information, packed into a fairly short book. It's a good companion to Digital Copyright, and well worth reading for anyone interested in how IP works (or doesn't work).

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

Blaine Hilton writes "Stealing the Network is a refreshing change from more traditional computer books. The authors have created fictional stories based on non-fictional concepts that could really happen to our computer systems today. The realistic fiction approach makes the book much lighter to read and actually entertaining. I also believe this approach makes the true methods behind the fictional stores much more memorable then memorizing thousand page textbooks." Read on for his overview of the book. Stealing the Network: How to Own the Box author Ryan Russell, Tim Mullen (Thor), FX, Dan Kaminsky, Joe Grand, Ken Pfeil, Ido Dubrawsky, Mark Burnett, and Paul Craig pages 328 publisher Syngress rating 8 reviewer Blaine Hilton ISBN 1931836876 summary An interesting fictionalized approach to hacking and other aspects of information security.

I'm leery of books that are written by multiple authors because the writing style always seems to keep me off beat from jumping around, however in this book it works out well since the book is organized as a series of short stories. Each story describes somebody involved in information security -- either somebody trying to access a system, or a person trying to keep the bad guys out.

If you are looking for a step-by-step guide to locking down your computer and network, this is not the book for you. Instead, this book is more to help people who already have at least a basic understanding of information security to see from another perspective. Stealing the Network looks at other reasons why people can break in: everything from being told to go to industry conferences to not collecting access cards when an employee leaves the company. What this book left deepest in my mind is to trust nothing, and assume even less.

After the ten short stories of how hacking is really done, there is a nicely done appendix along with Ryan Russel's "Laws of Security," which finishes this fictionalized book in a very non-fictional way. The laws cover most of the problems with current IT infrastructure, but do not go in-depth with what I believe is the biggest security hole, the user. Many of the stories touch on this fact but that's about the extent of it. I believe this may be because there are not any easy solutions to human behavior. This book says it best with "people are lazy."

At 328 pages (in pretty large text), this is a great easy read, though the book would be better with a lower price tag. However if you work with or around computers and the Internet, this book is very enlightening, if not completely informative.

Table of Contents

• Acknowledgements
• Contributors
• Forward
• Chapters:
  1. Hide and Sneak
  2. The Worm Turns
  3. Just Another Day at the Office
  4. h3X's Adventures in Networkland
  5. The Thief No One Saw
  6. Flying the Friendly Skies
  7. dis-card
  8. Social (In)Security
  9. BabelNet
  10. The Art of Tracking
• Appendix - The Laws of Security

Most of the book's authors have websites you can hit for more information; follow these links to find more from Ryan Russell, Tim Mullen (Thor), FX, Dan Kaminsky, Joe Grand, Ken Pfeil, Ido Dubrawsky and Mark Burnett, as well as Jeff Moss (who wrote the forward).

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