The last book I tried to use while at my computer was the first edition of the O'Reilly behemoth UNIX Power Tools, a small phone book in both page count and page quality. Working through a very large book of very many items front to back, as I did, might seem like a fool's errand. But Power Tools was, and in its third edition must still be, a tirelessly, relentlessly cross-referenced work. I was impressed by the vigor and care its contributors applied to relate so many points of information to each other. Moreover, I was struck by the implication that I could follow suit. It was a breath of encouragement I was grateful to receive, as I wanted to grow into power user status myself. It was also a gift I think about paying forward when I teach. Like when someone again runs off with my current copy, but in a way that doesn't stress the trust I place in my colleagues.
This book on DTrace, a technology for tracing process and operating system behavior, is also quite thick, and filled with many bits of information, hard-won from examining many dark areas of system and process code. The book is, in turns, a meandering journal, a breathless mash-up of contributions, a collection of clipped, man page-style narratives, and a dry series of code and output blocks the authors sometimes deem self-evident. Some clues, such as an oft-repeated warning that the fbt provider is unstable, suggest the book was built by force of compilation alone, with little interest in supporting a read-through, much less a systematic view of the content.
It is however a formidable cache, quite possibly including every DTrace program of general consequence written in the last few years. Despite protests to the contrary, it is also partly a tribute-to-self and tour de force of its lead author, and what he has done and can do with this technology. (I agree with another reviewer who found the preening on the back cover and introduction a bit too much.) The biggest benefit the reader receives from this work, then, are the products of that facility: scripts, recipes, power tools. Call them what you like.
But an 1100-page book of any construction needs some figurative handle to manage it. Unix Power Tools provided one with a display of cross-referencing heroics I doubt we will see again. After several attempts at cutting my own path, I downloaded the scripts and just started working through them, treating the book as a resource to clarify what I couldn't divine on my own. My results with that strategy so far amount to a coin-toss. To make full use of this book, I suspect most readers will have to meet the material more than half way, providing perhaps an uncommon passion, or considerable expertise. It would be better to bring both, and a continuous caffeine feed, to succeed.