Probe Books
Related Subjects:
More Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250
Used price: $0.01

Better than the first two books in the series, Tom is once again the capable inventorReview Date: 2008-04-09
Great Series to Introduce Young Boys to Science FictionReview Date: 2003-03-18
In the third story of the series, Tom must protect an alien space probe recovered from Io, one of Jupiter's moons, from theft while seeking to communicate with the artificial intelligence within. The story sets up the later works in the series as the probe helps Tom develop a hyperdrive and thus launch space exploration well beyond the moons of Jupiter.

Used price: $0.60

Very helpful for a challenging problem!Review Date: 2007-12-23
Auto MaintenanceReview Date: 2000-11-12

Used price: $2.32

great bookReview Date: 2008-07-19
It damns the dam with precise and powerful arguments.Review Date: 1999-08-29
There are a lot of detailed figures and facts in some of the essays. They're easily skimmed. But read this book if the subject matters to you and particularly if you're planning to take a cruise through the Three Gorges or have already taken it. While on the cruise, one is told only of the glory and power of the dam, which is to say, given the party line, but one should know the lie behind the line and the potential tragedy that awaits, the tragedy of the River Dragon coming again.


nice bookReview Date: 2006-02-12
covers the field, in 2004Review Date: 2004-12-18
Although, much work is still pure research. While some novel devices are described, the optimistic projections of mass scale industrial applications may still have to wait for a few more years.
Very useful to researchers across many disciplines.

Used price: $1.67

A must readReview Date: 2007-12-18
book purchaseReview Date: 2007-01-15
Not his best workReview Date: 2006-03-15
Crime fighting trilogy completedReview Date: 2005-03-29
had a personally emotional effect...Review Date: 2005-03-02

Used price: $0.04
Collectible price: $11.95

Clearly-written, level-headed analysisReview Date: 2001-08-08
I appreciated his step-by-step approach to clarify a process that can be challenging to understand. I also benefited from his detailed descriptions of how this kind of examination is supposed to be done. Fortunately, too, Dr. Ingermanson has a unique sense of humor which leavens a book that could otherwise be too dry to appreciate: the start is a laugh-out-loud point. But overall, the book is serious and well done, but readable and relatively easy to follow. However, there are parts that should be read slowly (or more than once) because the reasoning is not intuitively easy to grasp.
He builds his reasoning on a firm foundation, continuing to what I found to be an unavoidable conclusion. In addition, he makes sure that he's explained each topic/chapter before continuing. He discusses the other books on the subject courteously: when he disagrees with other authors' analytical methods, he never doubts their motives, but always gives them the benefit of the doubt. And when he disagrees with their conclusions, he does so courteously.
He pretty well debunks the code, and I appreciate his doing so. I find it hard to believe that God would bury information in His Word in this way. It would give the Bible a seek-and-find-puzzle aspect that would be beneath It. It's worth the effort to go to his website to find more information about this topic. He also lists other sites which are likely to be useful, too.
here we go again!Review Date: 2007-05-13
I recall stumbling across some fellow named Rashad Khalifa several years ago who determined--stop the presses!--that he is the Seal of the Seal of the Prophets; that the number nineteen is mysteriously coded into the Koran; that the world will end in the year 2280; etc. One can do all sorts of fun and fascinating things with a computer, but none of them will change the fact that, if I get to the tailor's shop three minutes after he closes, then I won't be able to retrieve my shirts.
Folks, there's something painfully obvious to be gleaned from all of this. The legitimacy or illegitimacy of the Torah code is utterly irrelevant. Postulating that there is an Almighty and that He wrote the Torah, would He have bothered to play mathematical games--bobbing up and down over there, surfacing for air "Thar she blows!" over yonder--or would He have allowed man to apply his own heart and mind to resolve the Fundamental Question? Concentrate on the message, and never mind the messenger and his bag of mathematical stunts. While you're at it, look up the Buddhist jataka of the blind men and the elephant.
DisappointingReview Date: 2002-01-03
I looked forward to reading this book because I was interested in seeing a well-reasoned refutation of the bible code
nonsense. It was not to be. Much better information is available for free on the net. I do not recommend this book at all.
First,
the annoyingly casual writing style really put me off. But I can overlook that in a book if the content is useful.
Unfortunately,
most of the book has nothing at all to do with a critique of the original bible code method. Instead, Ingermanson goes on
and on about his entropy method of looking at the ELS phenomenon. This is irrelevant because the original bible code paper
concerned statistical properties of related word pairs, and does not imply any necessity for individual ELSes to occur more
frequently than expected. Therefore, if one looks at some pro-code sites, one will see Ingermanson's book dismissed as irrelevant,
which it mostly is.
Of course, these same sites either ignore the really powerful critiques, or indulge in personal
attacks against the critics. But Ingermanson's argument is so lightweight, the zealots aren't even worried about him.
Eventually,
he does get around to discussing the famous rabbis experiment. He incorrectly accepts the math of the original code paper
as valid - apparently he hasn't studied some of the papers, freely available on the net, which point out how the original
paper didn't even present a proper statistical experiment. It is disappointing and surprising that Ingermanson wastes so much
time on entropy and then totally drops the ball when it comes to analyzing the original paper.
Of course, Ingermanson
decides the bible code doesn't exist, because of his irrelevant entropy argument. His response to the rabbis experiment is
to state that the data must have been tuned. He should have simply analyzed the original paper and explained how the statistics
were flawed. This would have been much more useful in debunking the bible codes. Stating that the original data must have
been tuned because of an irrelevant entropy calculation is very weak and only plays into the hands of the zealots.
My
advice to readers who seek the truth? Don't bother with this book. The whole codes business is debunked very successfully
on the net, for free!
On a non-scientific note, Ingermanson ignores one of the central issues for the Torah, which
is why are we even paying attention any more to this violent, primitive book which advocates mass murder? Why does he revere
this book? He doesn't explain.
Conclusion: this book is an ineffective rebuttal of the codes from someone who has
some science degrees but who is also religious. Perhaps this explains why he does not really tackle the problem head-on?
Thourough Debunking of the CodesReview Date: 2003-02-05
a confused scientist?Review Date: 2003-02-03
It's about faith that is playing a big part of this book... However, it reveals some interesting bits and pieces of info that can't be found on major media...

Used price: $0.01
Collectible price: $14.00

Excellent book...Review Date: 2007-11-16
It's not stated directly, but the book ultimately makes a great case for the further use of unmanned missions as the most cost-effective way to do scientific exploration in space, as opposed to the stunts of manned missions to the Moon and Mars. The present success of the Cassini mission to Saturn and the Spirit and Opportunity rovers on Mars is making the case stronger still, that unmanned missions are the way to go if you really want to do science in space.
Nice appetizerReview Date: 2004-05-03
Over all : a good book to get you started on solar system science
-kg
Good Historic SummaryReview Date: 2004-03-10
This book should prove of great interest to engineers involved in space and ocean exploration where technical failure is a constant threat. Those who practice engineering understand that learning how things fail is as important as learning how things succeed and Kluger has shown several examples of the engineering difficulties and work arounds that led to the most far reaching and remarkable exploratory effort in human history. From a scientific perspective the author has done a nice job summarizing the scientific interests and expectations for the known moons in the solar system.
This book will prove to be a good one source reading for a concise summary of planetary exploration to this time.
Excellent read.Review Date: 2004-03-03
The book is arranged chronologically and begins with the Ranger program, which was intended to send probes crashing into our own moon. This may be a program readers under 30 or so will have very little knowledge of (this reviewer is slightly older than that and still had little working knowledge of it). This portion of the book is most effective in its descriptions of the personalities involved (again, most of whom most people have never heard of) and the long, tedious, error-prone process by which these things got off the ground and to their eventual destination. The descriptions of the various problems that caused the first Rangers to fail is enlightening and shows how difficult spaceflight was (and is) even when the mission is fairly simple. Also of particular interest is the effects of failure on programs and personnel; recent events regarding the shuttle fleet show that constant vigilance on quality and safety issues are a recurring, probably an intrinsic, problem within NASA and really any organization.
I would have liked more discussion on the followup Surveyor missions, but from that point focus shifts outwards to the outer planets, and Mars and Venus. The Voyager program is where the book hits its stride, describing the inception of the program and the tradeoffs that had to be made within congressional budget constraints. Also fascinating is the explanation of how these things are navigated through space a billion miles away, a tedious job that most people don't think about. It is sure to increase our respect for the accomplishment of flying a small, barely-powered spacecraft to within a few thousands of miles away from a moon from over a billion miles away. It was truly an extraordinary accomplishment.
The later missions, Casini and Galileo, are probably more familiar to most readers so the novelty somewhat wears off at this point. There is still a good deal of useful information, much of which did not make it into the general news media so it is worth reading for this reason.
The great strength of the book is its descriptions of the spacecraft systems themselves and the personalities that built and flew them. The instruments, how they worked (or didn't), and the myriad of small things that had to go exactly right for the mission to succeed makes this book an excellent read for the technologically interested. Just as remarkable are the systems that didn't work and the ways the engineers and flight controllers worked around them. Less effective, though necessary of course, are the scientific examinations of the moons themselves and what was learned about them. However, this is a minor quibble and Kluger handles these issues effectively, providing enough detail for context but not getting bogged down in planetary detail. All in all, definitely a worthwhile read if you are at all interested in this aspect of NASA's history of unmanned spaceflight.
Great Book - The best account of US Unmanned space exporationReview Date: 2007-04-18
Used price: $0.11

Fascinating idea...Review Date: 2008-03-08
This near-future novel gets more and more involved as Hansen is drummed out of work and suspects a conspiracy. He's right, but he has no idea HOW high the conspiracy goes. Ed Lerner, a research engineer, has woven a Crichton-like story with intelligence and science that keeps you reading chapter after chapter..IF you like this kind of stuff.
Lerner certainly know HIS stuff..the tech is spot-on and readers may quibble with some things, but generally it's a good bedtime/airplane/vacation read.
this was an exciting, thought-provoking, easy read.Review Date: 2001-09-12
Especially fun to read a book with Chicago suburban settings that I can recognize
Excellent mix of technology and lovely possibilitiesReview Date: 1999-02-01
Interesting, but has a few problems.Review Date: 2004-07-02
In feel, I think it comes closest to "The Terminal Man," by Crichton. A number of different sciences and technologies get to play their parts, most (but not all) showing that the author knows what he is talking about. Weakest is the non-technical, office-political axis of the story. The reader may feel this dimension lacks the same first-hand contact the others do, for its author.
Regardless, it's a good book with some neat ideas and a few good twists, set in the Very Near Future (an era that is, IMHO, underused in fiction). If like Crichton, or books like, "Oath of Fealty," you'll probably enjoy this one.
Can a SF Thriller be any better? I dont think so!Review Date: 1997-06-09
His first and only SF novel is a high energy tale about mankinds first contact with a probe possibly sent by aliens from outer space. What starts like a common first contact story quickly evolves into a complex and intriguing plot about knowledge, power and the means to sustain it: coverups, treachery and deceit.
If you liked Crichtons SPHERE you will LOVE probe! Lerners style of writing is as complex as the plot itself but immensly entertaining. Believe me: This is an ALL TIME HIGHLIGHT!!!

Used price: $10.86

It's a Rough World Out ThereReview Date: 2005-05-26
Anyway, Snort is another tool in stopping the bad guys from coming into your system. In particular it is an intrusion detector. Note the word detector. Snort monitors your system to see what's happening. It is not an anti-virus like program that detects, quarantines, deletes, etc. an infected file. Instead it watches what is going on in the system and looks for behavior that is outside the rules.
Snort watches, records and reports on what the systems in you network might be doing. On a big network, running Snort could well be a full time job. It can produce volumes of information. Some of this information regarding your employees might be considered spying on them, there are also some words (a few more wouldn't hurt) on what you can do to outsiders vs. your own people.
Good but not a tutorialReview Date: 2005-05-21
As there is plenty of material at http://www.snort.org/docs/ and as getting Snort running isn't all that complicated anyway, that's not a major flaw.
Like another reviewer here, I think the rules sections are probably the best part of the book, though I was also impressed by the attention given to the specifics of Windows and Mac OS X - it's nice to see that level of completeness.
rules are the core of SnortReview Date: 2005-04-25
Of course and inevitably, the default rules base has grown and it is regularly updated. Currently, these defaults number some 3000, and few sysadmins have the expertise to understand all of them. So one recipe tells you how to get and run an updater program (Oinkmaster). Though you are cautioned about letting it change your rules automatically.
Other recipes expand upon the rule scope in interesting ways, like looking for p2p or Instant Messaging traffic. You might be responsible for a corporate network that bans these, perhaps. Here is a simple way to show a supervisor how you can stay on top of the problem.
Snort Cookbook a second glance!Review Date: 2005-09-29
by: Orebaugh, Biles & Babbin
What can I say designing a reliable detection system is a challenge at best.
This book makes it seem easy! I thought this was the best layout of a tech.book I have ever saw.
Problem > Solution > Discussion. they gave you the information in a precise way with out overloading you
with material you did not need. The Rules section was espcially useful...
The only downside is I wanted to see more on rules with samples.
Overall this was a very useful Book. I already had snort in place this made it much more useful.
Brett Hoff
Good information overshadowed by outdated or poor adviceReview Date: 2005-08-09
The Snort Cookbook starts poorly with ch 1, which at 50 pages is the book's largest. After repeating installation instructions covered in online resources, the book turns to dubious packet collection recommendations. Item 1.10 suggests creating a listen-only Ethernet cable but never mentions disabling ARP traffic with ifconfig's -arp option. Item 1.11 describes how to build a homebrew tap but doesn't address signal regeneration problems that could result in traffic loss.
Item 1.12 gives terrible advice: "If your Snort machine has only one network interface, using the passive tap, run both lines to a small hub. Then from another port of the hub, run a cable to your IDS. This will combine and maybe even buffer the traffic for the IDS and give a full duplex connection." Wrong -- this is a nice way to never see traffic when full-duplex packets from the two transmit lines collide in the hub.
Item 1.14 says "Snort itself is incapable of sniffing a wireless network," but it ignores the fact that while Snort doesn't understand 802.11 traffic, the sensor can join a wireless network and interpret what it sees. Item 1.15 demonstrates more ignorance of hardware issues by saying "Linux-compatible gigabit Ethernet cards are available with up to six ports. Coupled with machines that have space for three or four PCI cards, you could have as many as 24 Ethernet ports." This suggestion completely ignores the fact that a single gigabit NIC will saturate a 32 bit, 33 MHz PCI bus, and many BIOS will not be able to handle interrupts from more than about 8 NICs in a PC.
Item 1.25 says "two to four million records is the max for MySQL," which is odd. One MySQL database I use to collect session data on Sguil has over 31 million records. Item 1.25 also covers the often-repeated and incredibly naive method of having Snort log directly to a database, without utilizing Barnyard as an intermediary. Thankfully we see Barnyard covered in ch 2, but recommended for "high-speed network[s], such as 1 Gbps or greater." Barnyard is definitely appropriate when monitoring at less than gigabit speeds.
Throughout the book, the obsolete ACID Web-based alert console appears. BASE has been available since October 2004; it addresses stale code problems in ACID and should have been covered. I was disappointed to see the Sguil suite mentioned but never given any discussion, even though the older Snort 2.1 book introduces using Sguil. Item 4.2 mentions "RST scans" even though they are a fiction of one security researcher's imagination. Item 6.6 claims to offer ways to test Snort by showing three programs (Snot, Sneeze, Stick) that have had little effect on modern Snort implementations (e.g., 2001 on).
On the positive side, in many cases the Snort Cookbook properly addresses questions which frequently appear on the snort-users mailing list. Items 2.15 and 2.16 show how to send Snort alerts to email, a pager, or cell phone using Syslog and Swatch. Item 3.2 discusses rule updates with Oinkmaster. Rule issues in ch 3 were generally helpful, like dynamic rules (3.4), evasion issues (3.10), optimization (3.13), and even Spade (3.18). Perfmon coverage in items 4.6 and 7.0 help discover how well Snort is working. I also liked the policy-based IDS ideas in item 7.5.
The back cover of the Snort Cookbook says the book "can save you countless hours of sifting through dubious online advice or wordy tutorials." That online advice is frequently more correct than what appears in this book. While some of the book is helpful, often that material has already been introduced in online documentation or best covered in Syngress' Snort 2.1. Perhaps a second edition will address the concerns in this review and produce a more useful cookbook for future readers.


More mystery or horror than science fictionReview Date: 2001-09-20
More mystery or horror than science fictionReview Date: 2001-09-20
an entertaning cross of genresReview Date: 2002-12-06
In my opinion, the story had much more potential as a horror novel, with a good spooky original idea and great setting places. One thing about reading a book that is a part of series is the preprogrammed notion of the invinsibility of the main characters, which taints the whole idea of a good scare. Although that does sound rather morbid:)
With the exception of Carson/John, the characters didn't do much for me,as they kind of lack that "certain something", however seemed well developed and rather believable. The real star of the "production" was definetely the idea behind the story itself. I would have given it about three and a half stars, but it was overall an entertaining read and I guess it put me in a generous mood:)
I couldn't wait for the last page to see what happened!Review Date: 1999-07-21
Related Subjects:
More Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250
In this story, Aracta is stolen by the villain of the previous story and flown to the asteroid belt, where the evil David Luna takes control. Luna is a rich, powerful and ruthless tycoon who is the Swift Company's main rival. With the help of the quick-thinking Aristotle, Tom and his group are able to escape with Aracta. The story closes with a discussion of the structure of the star drive and the possibilities for aiding the Skree against the Chutans.
I found this book to be better than the first two; Tom is once more the capable inventor, which is the whole point of the series. Another improvement was that Tom's father only has an incidental role at the beginning; in the first two books he was too much of an imposing father figure, which tended to diminish Tom.