Computers Books

Network Warrior is another quite useful O'Reilly effort in the Cisco handbook space. It really is potentially handy for many real-time network operators. One thing I wish the author had spent much more time on is Ethernet switching. He does dig into some of the quirks of configuring VLANs in the Cisco environment but to my way of thinking associated subjects (mirroring, span port config, spanning tree troubleshooting) need a lot more exposure. One area that cannot be talked about enough are the twists involved in setting up spanning tree through a complex VLAN network. Another potentially vital topic involves interoperating with other vendors' equipment in a spanning tree network. I bought this book hoping for more exposure than I got in those areas. This is the only reason I didn't give it five.

One of the best networking books I have read, period. Not just how it works, but why it works and should be configured. After you study and obtain your CCNA, this is the next read that will fill in many information holes.

Highly recommended.

In preparation for the CCNA exam, I have gone through several networking books, both Cisco-specific and otherwise. I had thought that the official Cisco Press CCNA set was the best resource... until I took a chance on this tome. While I have found the Wendell Odom CCNA set to be the definitive guide to CCNA/CCENT material, I now must admit that this book is nearly - or even exactly - as essential as a CCNA exam prep guide. While the other guides read like textbooks, giving the reader adequate conceptual and theoretical information, this book felt like a nice long chat with a seasoned "network warrior" about real-world, everyday issues faced by network engineers.

What set this book apart from the thousands of pages (hey, I'm dedicated!) of material I'd already covered?

- CatOS commands; the new Cisco Press books barely mention that CatOS exists!
- anecdotes and real-world examples; even if you know how it *should* work, this book reveals how it *does* work
- objective viewpoint on Cisco technology; no "Cisco's way is the best way" dogma here
- meaningful discussion of high-end, core-strength equipment; everything in the Wendell Odom set focused exclusively on Catalyst 2960 switches and one model of router
- frank, direct, humorous, and engaging style; half the material I've covered previously was dreadfully dull
- illustrations for every concept; this makes my life so much easier when trying to explain things to fellow junior technicians

While the book may seem daunting at nearly 600 pages, I'm flying through it at about 80-100 pages per day. The text is very engaging, and the author's way of phrasing things is informative and structured yet very flowing and casual. I feel that every chapter contains some point, if not several points and concepts, that I wouldn't have known from the other books out there. What is possibly the best feature of this book is the real-world, realistic approach to every concept and issue. The Cisco Press books seem to assume that the reader will be using 2960 access layer switches running IOS 12.2 or better. Network Warrior does not make this assumption. The author makes the realistic assumption that the reader's network could have all kinds of gear networked together, and thus includes information about CatOS as well as a wide variety of Cisco hardware. Also included are some quick and dirty tricks to save time, money, and effort. For example, I didn't know that I could abbreviate almost any command in IOS ("sho" instead of "show", etc.) and still get the same result until I read this book. While I feel that the by-the-book approach of the Cisco Press material is necessary for building a clear foundation, I feel that this book's get-the-job-done take on networking is a necessary follow-up.

The book assumes some working knowledge of networking, but not too much. It doesn't explain the bare basics of networking, nor does it give a history lesson about the histories of each and every cabling standard and networking protocol. It's not a total replacement for a book about networking basics, nor a beginner's guide to the CCNA and/or Cisco equipment. What it does instead is reshape one's conception of what a network is and how to manage it. What it does as well, and does excellently, is fill in the gaps that sorely needed filling in the great mass of other Cisco material out there. If you are preparing for the CCNA, or if you have already passed and think you know all you'll need to know about managing Cisco networks, this book was written for you. I guarantee you will learn something new.

Great book. Highly recommended for anyone who needs intermediate network skills. Go beyond your entry level cert. I got this and the linux network cookbook plus some Red Hat specific material to prepare for the RHCE- should keep me busy for awhile.

This book won't help you become an OSPF expert, but it will help you become a better network engineer. It's one of the only books I've every seen that embraces the fact that our jobs have a gruesome amount of logistics inherent to them, far more than a programmer or DBA, for example. I'v spent the last 2+ years at MySpace, and Donahue's descriptions of the problems faced by explosive growth brought a tear to my jaded, burnt-out eye. Finally someone understands we're not just idiots! (If you disagree, try scaling from 10Gbps in transit to 80 in one year, then shoot me an email :) ) Even better, since his anecdotes and advice on the practicalities of our niche are often only mildly technical, they're easy to read. I was able to blast through 100 pages at a time, often laughing and nodding, while still learning a new spin on simple things like IP address allocation.

On a more technical level, this book fills a ton of gaps that aren't covered anywhere else, or the documentation is difficult to find or understand. The section on storm-control was excellent in this sense. If you do nothing else, go to Borders and read that section. It's useful information in its own right, but demonstrates Donahue's tendency to spin something simple in a way that shows you something new. I picked up a lot of weird details in this book, even if I skimmed half of it.

I also noticed a lot of his sidenotes pointed out some very common pitfalls, such as appending a space to your password in PPP on one side of a link by using the context help, then not doing so on the other end, and wondering why your stupid link won't come up.

So what are the cons? None really, just a few things I would have liked to see in there (none of which detract from the 5-star rating).

- I would have liked to hear how Donahue approaches the issue of spares and money, specifically convincing management to buy spares, or hiding them in budgets
- The NTP section could have used a blurb on anycast, which works beautifully for NTP
- I would have liked to see him mention the troubleshooting assistance that change management provides, since if something breaks and your engineers issued a change request, you pretty much know where to start
- I'm also a huge fan of peer-review for CM, as having a manager rubber-stamp your ACL update is ... of limited technical value

I'd say that, along with about 5-10 other books that go into hardcore depth on various technologies (Doyle's routing books, Halabi's BGP, QOS Voice exam guide, etc.), this book should be on a shelf near you at work. If you're already pretty advanced it's a really quick read that tosses some golden nuggets at you when you least expect it.

One more thing, since one guy punished the book's rating for being Cisco-centric, I'd like to take a moment to point to the Book Description, specifically the part that says, "Network Warrior is a Cisco-centric book". If you're at a book store (do they still exist?) and thus do not have access to this description, please see the first paragraph on the back of the book, specifically the part that says, "...helps you deal with real Cisco networks..."

THIS BOOK MAKES MY FRIEND CRAZZZY ABOUT MELALEUCA. HE IS A GREAT PERSON AND BELIEVES WITH ALL HIS HEART IN MELALEUCA. I THINK THAT IT IS A GREAT COMPANY AND I WOULD SUGGEST YOU TO INVEST IN ITS PRODUCTS HIS NAME IS ROBERTO ZUNIGA HIS TELEPHONE NUMBER IS 1 631 816 4690 HE WORKS WITH THIS BEST SELLING AUTHOR. GIVE IT A GO AND TRY THIS AMAZING AND UNIQUE CONCEPT.

Russ really has the ability to not only do but also to concisely and clearly make known what actions to take and not take while building a network marketing organizaton.

Anyone who reads and applies these steps should surely experience success.

This is not a feel good book, motivational book, or a book on self improvement. This a book of facts and information, valuable facts and information, that if learned and applied will enable the reader to reach their fianacial goals. Outstanding! It is a must have for anyone wishing to gain have control of where they are going!

I have never been so impressed with a networking 'hands-on' book as I am with "Network your way to Millions" by Russ Paley. In my 14 years as a network marketing trainer I have had the honor of prospecting and helping such greats as Richard Kall, an icon in the industry. Russ has captured the true deliverence for the beginner as well as the seasoned professional in his long overdue masterpiece. Paul Kupetsky aka The Midas Muffler Man.

RUSS GIVES STEP BY STEP INSIGHTN ON THE BUILDING OF A NETWORKING BUSINESS. A MUST FOR ALL LEADERS

Until Mac OS X came out this book helped me with _every_ hardware and software problem that ever turned up!
Only once one of my Macs was actually beyond repair, but ever since 1999 this book really saved the day.

The iMac I purchased in July 2001 is my first home computer. I found this book at the library, then discovered it contained so much good information, that I purchased it. It sometimes has too much info for a newbie, but still it is an excellent reference. This book is the "bible of troubleshooting", and a great way to learn how your computer works. I'd say it is a "must purchase"!

The iMac I purchased in July 2001 is my first home computer. I found this book at the library, then discovered it contained so much good information, that I purchased it. It sometimes has too much info for a newbie, but still it is an excellent reference. I use 2 other books along with this one, to trouble shoot and confirm resolutions to any computer problem. This book is like the "bible of troubleshooting". I'd say it is a "must purchase"!

One of the few technical books in my library that I feel has really paid for itself, and then some. Technical books are so expensive, and most of mine sit in the bookcase collecting dust within a month or two after purchasing them. This book had saved me more money than I spent on it within the first month, and I continue to use it on a regular basis. In addition to having real and practical advice on fixing problems, Mr Landau provides advice on preventative maintenance and must-have troublshooting aids, and background on how Macs work when thre aren't any problems. I would say that this book is the most essential of those aforementioned must-have tools.

I have a lot of respect for Landau .. and he knows what he's writing about ... but this was written pre-OS X.

It's time for another edition, since OS X has a whole NEW set of problems ... including the occasional "kernel panic" (read "crash"). There is also a whole new group of compatibility issues with peripherals: printers and scanners among them.

What a great resource. For a small biz like myself, it gives simple, concrete "growth" advice and direction. It should be in new print...not relegated to the used marketplace. With so much fodder out there, this stands way above the pack!

I keep referring to Parker's book over and over again. Even someone who has been marketing via the Net for several years will find this text a cogent, insightful and organized source of help. I can't imagine my Web-based efforts without its guidance.

Most books published this long ago look incredibly dated by now. This one isn't. Everything in it still rings true, and it's a shame more websites don't heed this man's advice.

I've been marketing and selling on the internet since 1995. There is one specific idea in this book that IF you actually use it, you will almost certainly triple your business. (No kidding) I definitely wish I would have had this book 5 years ago. However, I have it now and the fundamentals are superb. Parker takes you through the strategies that bring people to your web site and develop a web site that gets people to come back again and again.

I absolutely love this book and strongly suggest you pick it up. ...Isn't it worth it to gain some powerful, usable and workable strategies that will make you 1000 times the investment?! It's a no-brainer!

Kevin Hogan...

I bought the book because I saw a lot of great reviews about it on amazon.com. But after reading the book, it's really disappointing because the book is just very shallow about web marketing... It's also very repetitive and all it says is very general, it doesn't really cover much on strategic web marketing. A lot of the articles on the many web marketing sites or newsletters out there are much more helpful than that book. It doesn't tell much except for mentioning repeatedly how good content, customers registration and email newsletters are important for relationship marketing... It doesn't provide any resource at all for the readers to create good content, to build a customer email database or to launch an effective promotion or marketing campaign, i don't recommend this book at all.

item was delivered in a good condition but it was not shipped to my address even though I specified accurate address with apt number. I had to pick it up from post office!

Thumbs up. There are lots of reviews there already, and what they say are mostly true in my opinion. It is a good book to read to get general basic knowledge of Database. However might not be as good if you want to learn a specific database software. The book is written in simple and clear words, and is very organized, which is a huge bonus in my rating.

The book is very helpful for novice learners of databases. It provides step-by-step guide to those who are new in database design and Microsoft Access. Key concepts like normalization are presented very clearly with relevant examples in business.

I found this book to be really dry and not at all demystifying! It went in depth into the history of databases, who created them, and why it was groundbreaking. I'm sure that's very interesting to some people, but not to someone who is trying to make sense of it all. The author seems to have had a difficult time determining what is necessary for comprehension and what is merely icing on the cake for trivia fans. Since he couldn't make the determination, he just included it all! If you are a computer technology science major or something, you might like this book. If you just want a book to help you to understand databases in general (as a foundation), this is not the book for you.

There are two things in life that are difficult: databases and comedy. Fortunately, the author makes understanding databases far less difficult with his clear explanations and examples. I confess that some aspects of a database (and I have some experience) are still a mystery, but I hurriedly read this book because I have some much reading to do. Sometimes, the best use of your time is to slow down and let concepts mature in your mind. Even though I hurried through the book, my understanding of databases deepened and I intend to read the book again, taking more time to understand some of the concepts that are a little fuzzy. This book will not waste your time. The author is talented and is skilled in the art of instruction.

This book is a must if you are learning BSD Unix. All the commands you'll ever use are covered in this book. This book is easy to read and explains important topics without being exhaustive (a skill some authors never learn). A great book for newbies to BSD Unix!

If you're looking for a place to start with FreeBSD (or with open soruce in general), this is really the book to get. I knew a little UNIX before I picked this up, but essentially I was a babe in the woods. This book helped me get my system up and running with clear, task-oriented discussions of all of the essentials. This doesn't go as deep as some of the other FreeBSD books out there (for that you'll probably want "Absolute BSD" by Michael Lucas), but it does tell you what you need to know to get started.

I bought the book after I had installed a broken FreeBSD 4.7 on my old AMD K6-II. Despite the few typos here and there, the book helped me figure out what mistakes I had made during my previous installation ! I thus re-installed from scratch, following page by page. In no time, the system was up and running, I was customizing my shell behavior, connecting to the internet through my cable modem (Roadrunner/Earthlink), etc...

With some extra hardware, my old AMD K6-II is now a router/firewall between my cable modem and my WinXP/Red Hat 8.0 dual-boot box without a glitch, and am planning to add a second box to my LAN and use it as a printer server too.

For those who still hesitate, this book is written in english, not in nerdish. That itself makes it stand out from all the computer litterature I've read. This book is very valuable.

Annelise: your book made my hardware firewall project feel like a walk in the park. Thank you so much !

I first tried to install FreeBSD 4.8 on my K6-2 500mhz machine using the FreeBSD Handbook as a guide. While this book (the Handbook) is the standard for reference on the subject, it doesn't really explain it to a newbie's needs (even someone coming from Linux). My first attempts failed. I bought Annelise's book and was able to get 4.8 up and running following her suggestions. Though my copy came with a CD of FreeBSD 4.7, I had already burned ISO images of 4.8. The processes detailed in the book applied equally well. My only complaint would be that the book needs updating to reflect areas that a lot of people (most people) are interested in these days: burning music to CD - especially ATAPI CD devices, and USB mass storage devices. Both could be covered by a chapter on how to use SCSI emulation. I still give it 5 stars.

I had been getting fed up with using Windows and wanted to learn a new operating system. I bought Anderson's book and installed FreeBSD 4.6 on an extra hard drive in my computer. The book covers a broad range of topics and I found it very helpful during the installation process. The first 10 chapters are great. I started to get annoyed with Chapter 12 on connecting to the internet. I used PPP and something kept going wrong. I still do not know what it was but the errors I got were endless. The chapters little sidenotes on troubeshooting were of no help and I eventually gave up. Then I tried to install the printer daemon and also recieved errors. I followed the book as best I could and eventually gave up and moved on. Chapter 14 on the X window system is great. Other than the printer and PPP problems (which could have just been my misunderstanding of the book), I would recommend this book to someone else

I bought three books to teach myself how to produce DVDs. The Erica Sadun book is for advanced users and was not helpful to me. The Bob LeVitus "Little iDVD Book" is probably one of the most poorly organized and edited books I've ever come across on any subject.

Pogue's "Missing Manual", on the other hand, is comprehensive, clear and well-organized. I've produced about half a dozen DVDs since reading (and re-reading) Pogue's book and it clearly made a huge difference in what I was able to construct using iDVD.

In my opinion, this is the only book you need to read to learn how to produce movies using iDVD.

Beyond teaching readers to work with iDVD, Pogue also offers loads of helpful suggestions about editing in general. This book is outstanding.

I love this book! I was ready to give up trying to use iMovie because of a small glitch that was incurring. After browsing thru the book the very first time I opened it, I came across the trouble I was having with iMovie. Mr. Pogue directed me to the correct settings and I am now having a great time editing my DV movies.

I would highly recommend this book to anyone attempting to use iMovie. There is so much more to this program than Apple addresses in the help file. Mr. Pogue's writing is concise but not out of reach for the average Mac user.

I have many books by Mr. Pogue and I would recommend any of them if you are stumped and need a well explained how-to-manuel.

Can it get any simpler !! ha ha ha ha ha
I found this book to be extremely informative and easy to understand (especially since i am yet to purchace a mac and digital video cammera ).. I will have no hesitation now to go out and purchase a Mac and a Digital cammera .. and feel confident making my first feature film or "Home Movie " LOL

It's OK. It has about the same amount of material as the "iMovie 2 for Macintosh Visual Quickstart Guide" - The missing manual is fatter because it contains additional stories and things that a reader might find amusing, but that are not particular relevant to the topic. The section on movie making basics is very good. For an expanded view see "The Five C's of Cinematography". I thought I would find more information in this book since it is fatter than in the VQG, but it ended up that they are about even in content.

First I have to give props to David Pogue and his Missing Manual series. As a bookseller and computer geek I've long favored the Dummies books as the best entry-level source for third-party information on software. However, O'Reilly made a smart move when they turned their attention on that market and grabbed Dummies standby Pogue to headline the new series. The Missing Manuals (and their mutant-dogcow mascot) are a credit to O'Reilly and a must-have... assuming, that is, that they cover the program you need. The series is still too small, but I'm sure it won't stay that way.

Now, to the book itself. If you need to do something with iMovie, it's in there. That pretty much covers what I need to say in this review, but it doesn't cover everything the book has to offer. Remember back in the 80s when the Mac made desktop publishing a reality, only to unleash a torrent of wretchedly amateurish graphic design? Well, Pogue spends much of the first couple of chapters attempting to prevent that from happening. This book starts off with a very basic primer on video production and how to use your equipment -- assumed to be a typical consumer-grade MiniDV camcorder, but it covers other options as well, particularly video bridges and the like.

The meat of the book discusses iMovie 2's capabilities, including discussions of its weaknesses and how to work around them. Effects, titles, and transitions are discussed in detail, including some useful information on crossfades (never fade straight to black -- instead, you want a black stillframe). Conversion to other formats is also an issue, and a significant part of the book discusses postproduction using QuickTime Pro. Directions are given for converting your work for DVD or VCD as well.

The issue I have with the book is largely its focus on iMovie in MacOS Classic, and the bugs that are present in that version that might not be in the OS X version. Screenshots all come from 9.x, with the only Aqua material being the interface of iMovie itself. I don't mark down for this since the program operates more or less the same, but an inexperienced user may have trouble. (I might note as well that the book works just as well for iMovie 3, which has a superficially different interface but handles more or less identically.)

So, yeah. If you're doing video production on iMovie, this is the book to get, hands down.

I work for a Fortune 500 company and was first introduced to Gerry McGovern through one of his workshops that my company was hosting. I really connected with Gerry's passion for both the customer's perspective, as well as his message to get the fundamentals right. Armed with his book Killer Web Content, I left the workshop inspired with new ideas for solving some of the UX issues we were having with our Careers website (strategic business tool for talent recruiting).

I started to read his book the next week and learned enough useful information with each chapter that I finished it. I got a lot of value from some of the techniques described in Killer Web Content. I appreciated the information specific to generating good content using "Carewords" in the right way and at the right time. I also learned from this book that the web user is a different animal than traditional application users. Gerry has a good handle on the machinations that drive this new information hunter's behavior.

I can honestly say that I've quoted Gerry's work in UX meetings dozens of times since first attending his workshop. Since December, I've given away three copies of Killer Web Content to other UX professionals. All 3 have given it rave reviews! In addition to attending one of his live workshops (absolutely awesome!), I HIGHLY recommend getting this book!

I have been a subscriber to Gerry's weekly e-mails for over two years. As a web editor for a large organization, his advice has guided me in my career and helped me enormously in every area of website management.

When I learned about Gerry McGovern's book Killer Web Content, I immediately ordered it. Because I was about to leave for vacation, I had Amazon ship the book to where I was holidaying - that's how excited I was to read it. Sure enough, I devoured the book, and (almost) couldn't wait to get back to work so I could start applying his teachings.

Killer Web Content is THE authority on how to have a successful website. Using real-life examples, it feels as though McGovern is having a conversation with you. His advice is invaluable and this book should be necessary reading for anyone creating a website.

I cannot recommend this book enough - not just for communicators and marketers, but for graphic designers and techies too. McGovern is a visionary and ahead of his time. YOU MUST READ IT!

I love when authors get to the point, and McGovern does it. A lot of this stuff is common sense, but it becomes more top-of-mind when someone writes about it. McGovern mentions some good tools to help write "killer web content," and while some of the practices he uses for testing content aren't necessary do-able for most companies/people, I'm still able to take away the basics and make them part of my process for writing web content.

I'm a usability researcher who's looking to get some concrete suggestions about how to write better for the web. That's what I was hoping to find in this book--a guide with detailed suggestions for how to do this type of technical writing. Instead, there are very few concrete suggestions in this book about how to write well, other than vague platitudes about keeping phrases short, and providing users with the content they'd like to see. Duh.

I read this thing cover to cover in about an hour. Mostly I learned that "killer" rhymes with "filler." A lot. If it has not yet occurred to you that you might want to talk to your customers about what they're looking for on your webpage, then I guess this book would be for you and would provide you with that revolutionary insight. That's all the advice there is in this book--talk to your customers to find out the content they're looking for on your webpage, and then deliver that content to them in small, easily digestible phrases. Again, duh.

For people who are just starting out on this type of research, there's really no detailed advice on how to conduct this "talking to your users to find out what they want" research though (other than some more platitudes like "be a good listener."). If you want more detailed advice on how to do research like this, I'd say search the web for "wants and needs analysis" because that's basically what this guy is recommending. If you can't find enough things for free on the web about that, there is a good chapter in the book "Understanding your users" by Catherine Courage on this technique. That book is also great for giving you a wide toolset of techniques for usability.

He also gets a little bit into persona creation, which is basically a fancy way of saying it helps to imagine who your customers are and have a picture of them in your mind as you design your user experience. Again, you can find free stuff on the web about this or check out Tamara Adlin and John Pruitt's book "The Persona Lifestyle" to get lots of great information about this technique.

If you're truly just starting out trying to figure out how to make your website better and you don't know where to begin, I think a way better guide is Steve Krug's "Don't Make Me Think." That book provides a great overall context for providing great user experiences in general.

I am looking forward to reading the new Ginny Redish book on this subject! Her stuff has been high quality in the past and so I expect she will have a bunch of actual information on how to write for the web as opposed to the filler in this book. It's pretty ironic that a book all about providing great content without a bunch of filler is...a bunch of filler. It was a killer for me but not in the way it intended to be.

The book is a good read with a lot of useful information about content design and production. Don't expect a detailed tutorial, it aims rather to show you what is important and what approach you should take.

What I liked
- rich information about user behaviours regarding content consumptions (debunks some myths)
- eye-opener findings (did you know that the word 'special offers' is preferred to the word 'deal' when people are asked though when searching, they use the word 'deal'? etc.)
- clear examples and reasoning that can help you in situations when you have to convince clients about some fundamental content issues

What I did not like
- if you have been following Gerry's newsletters as I did, well, you already know most of what the book is about
- there are some chapters that did not tell me really anything (one is about some very rudimentary SEO, another about the importance of blogging)
- the design of the print: there are complete pages written in bold red letters, some pages look like this is the first Powerpoint presentation with an ISBN number

This in-depth look into transaction processing provides a wonderful place to start when considering implementation in your application(s). Cover-to-cover, this is an EXTREMELY easy read and doesn't try to be "fancy" or use complicated wording as many other books on the topic do.

Before reading any other transaction books or jumping into API document, this is a MUST MUST MUST MUST read. When developing an application that has transaction support, this is wonderful as a reference in order to include data in presentations, summaries, position papers, internal documentation, etc.

No only will this benefit a general developer, but also benefit people not in the development environment. This allows for clarification of communication between departments without going into API-specific implementation details.

This book is excelent for who want to deep his knowledge in TP. Is very practical with many examples and tips. Funthermore include examples of of transacctions for commercials TP like a MTS (COM + today), Tuxedo, CICS, etc.
Is a book very very recommendable.
bye.

The title of this review is a quote from the book and it summarizes it very nicely. Indeed, the book provides a great deal of information in such a small volume, but many of the things that would have been nice to have are missing and many are just skimmed over.

The best chapters of the book explain in very simple words the principles of transaction logging (along with recovery from a failure), two-phase locking and two-phase commit.

The chapter on transactional communications is not as thorough as the just mentioned ones and pays most attention to transactional message queueing rather than synchronous RPC and peer-to-peer. On top of that, message queues are just transactional, period. No attention is paid to the message queues specifics.

The chapter on transaction processing monitors considers only the three-tier environment with presentation, workflow and transaction tiers.

Other problems ?

The whole chapter with an overview of the existing transaction processing software was useless. You see, product Foo has features A and B, and product Bar has features C and D, so what ? As you read it, certain architecture similarities show through, but it's up to you to analyze it, the book gives no cross-product comparison, no analysis, just a list of acronyms.

Samples in Cobol (duh !) or tangled C-like code. The pictures are less than perfect.

But the biggest problem to me was certainly the lack of real-life information. Specifically, I would better be interested in interaction between transactional and non-transactional systems. An acknowledgement of databases and message queues being the only transactional systems (or not) and the implications of that. Two-phase commit in heterogeneous environment. And so on.

A great introductory book.

Transaction processing is a daunting topic, and this is one of the few books that provides the basics in a clear, understandable manner without overwhelming the reader. Most of the book is focused solely on transaction processing, but it touches on queuing as well, which makes it the ideal first book for anyone who is seeking details that extend beyond pure TP.

I like the way that the authors use real products to reinforce key points made throughout the book. While some of the products are no longer mainstream (indeed, some were never mainstream), the fact that real world implementations are used makes the information realistic. If you are using CICS, MQSeries, Tuxedo or similar products this book will have even more value. I also like the way difficult topics, such as locking, high availability and database recovery are given entire chapters because these topics need to be thoroughly understood in order to completely understand transaction processing.

After reading this book you will be armed with sufficient knowledge to make intelligent choices in selecting the right approach for transaction processing in a system design, or to understand the nuts and bolts of any TPM that you are supporting. I also agree with Cem Kaner's earlier comments that this book is an ideal resource for software test professionals who need to understand the entire environment that they will be testing. If you want to go deeper into TP, I recommend "Transactional Information Systems: Theory, Algorithms, and the Practice of Concurrency Control" by Gerhard Weikum and Gottfried Vossen, which drills much further down into the details of both transaction processing and queuing systems.

This book was written in 1997 which is often considered ancient in "Internet-years" but it is still very relevant because it focuses on fundamental principles of transaction processing (TP) rather than the latest whiz-bang technologies that optimize TP.

For those of you who aren't TP experts, a transaction is a computer operation that meets the ACID test. ACID here stands for:

Atomic - the steps that comprise transaction succeed or fail as one, there is no partial success.

Consistent - the internal data structures of the system(s) remain consistent with business rules.

Isolated - the data read or manipulated by the transaction is not altered during the duration of the transaction's execution.

Durable - the results of the transaction are persisted

Why does this matter to the system user or stakeholder? The canonical example is that of the ATM machine (or the "handy bank" if you're Australian). When you withdrawl money from an ATM, it has to go out and validate you have enough funds to meet the withdrawl, reserve those funds, and dispense cash - all within the same transaction. If the ATM failed after your bank account had been debited but before you'd gotten your money, you'd be very upset; conversely if the cash was dispensed but the debit procedure failed, the bank would be very upset. Ted provides very amusing analogy for this using a wedding ceremony but you can read that in his book.

There's a whole lot more to transaction processing beyond ACID and the ATM example, including two-phase commit (TPC), high-availability, massive concurrency, and crash recovery. To find out about all of these topics, read the book. One thing to remember though is that most application developers will never have to deal with the extremely complex details of providing a working and robust transaction management implementation, but like any technology it's important to understand the technology's fundamental principles and mechanics to effectively use it.

The book itself is extremely dense. The content of the book is "only" 324 pages long but covers a large amount of ground in a good amount of detail. Definitely read in a quiet place free of interruptions with a strong cup of coffee.

One shortcoming of the book is that it was written in 1997 so it doesn't cover TP implementations in Java (e.g. JTA, EJBs, etc.) but it was nice to finally find out what the heck IBM's CICS and IMS products are.

Interestingly enough, I have never had to deal with complex transaction processing (i.e. two-phase commit) in my short IBM career. This is probably because I've worked on business-to-consumer (B2C) applications where only one data source is involved rather than a business-to-business system where multiple data sources are involved. I'll have to ask the B2B guys if they get heavy into two-phase commit or if it's not an issue.

The reason I read this book is because I've always been a bit mystified by Enterprise JavaBeans (EJBs). When I joined IBM, I knew the word, but I was not familiar with such topics as object-relational persistence, object remoting, and transaction processing, so to me EJBs were simply things that took four classes/interfaces to do what I could do in one simple POJO. Ted Neward, in a very interesting web interview on the Serverside.com mentioned that he used to think EJBs were completely worthless, but during the process of writing Effective Enterprise Java came to realize that they were not worthless but rather over-marketed. He said that they should have been called Transactional JavaBeans rather than Enterprise JavaBeans because transactions are what EJBs did very well. So, hearing this from Ted I decided to read a book on fundamentals of transaction processing, so that I could understand EJBs better. Now that I've read all about TP principles, I pick Richard Monson-Haefel's book again, and all of a sudden EJBs start to make a lot more sense.

I finally picked up this book last year and throughoughly enjoyed it. I keep referring to it because the examples build up to the point of qualified proof of concept. The examples also are different enough from the other ones that are easy to find with Google, so between the two you get a complete view of the vulnerable issue.

The book's title should be obvious enough; this is NOT a book of defenses. However, if you understand these attacks you will be better equiped to deal with them when they happen. This book is no replacement for hands-on training in person with a qualified instructor such as at the SANS Institute, but it is an excellent supplement.

Its a great place to start...and works its way through some pretty indepth concepts. The great part is that for the beginner it is step by step....and they tell you were to download everything you will need. Anyways loved it, read it twice.

I have been around the software industry now for almost 20 years and every now and then I find a book where I learn exciting things, this is one of those books. It reminds me of the early days of low level Windows programming but with very up to date information on the OS and how to apply it. The book is obviously designed to attract hackers - both black and white hats - however it does do a good job diving on the internals of the Posix and Windows subsystems. If you like low level stuff this book is for you.

Not an easy read if you're not already familiar with programming and operating system concepts, but then if you are an IT security professional you'd better be, and the book explains why.

I read Rootkits: Subverting the Windows Kernel last year, but waited until I read Joseph Kong's Designing BSD Rootkits before reviewing both books. In a head-to-head comparison, I thought Kong's book was easier to comprehend and directly covered the key techniques I wanted to see. If I could give this book 4 1/2 stars I would, but Amazon doesn't allow that luxury.

Hoglund and Butler should be commended for writing this book. It really does assemble the parts (meaning techniques and code) necessary to implement a Windows rootkit, at least prior to Windows Vista. My only concern is that, at times, the authors are not as clear as I hoped they might be. This is probably due to the fact that they are two of the best rootkit writers on the planet, so they probably do not remember what it was like to not understand "hooking" and other techniques.

In some ways Rootkits is probably a book best suited for other experts (like many who wrote reviews here). That leaves beginners (like myself) wishing for a little more foundation or direct language prior to reading about implementation tricks.

One of the greatest strengths of this book, however, is the degree to which it exposes the internal workings of Windows. For greatest effect it's probably worth reading Microsoft Windows Internals, Fourth Edition by Russinovich and Solomon first.

Note that although I found the direct approach of the BSD rootkits book better for my learning style, this book by Hoglund and Butler is deeper in several areas. In fact, those who liked the BSD rootkits book would do well to read its Windows counterpart to learn tricks from Hoglund and Butler.