It's kind of impressive how comprehensive Google street view coverage has become.
Completely zoomed almost all of North America and Western Europe is covered in the distinctive blue halo. From there you can fly your little yellow traveler across tremendous distance and watch the street preview display yet another country side scenery. Or you can drop it and guess where you landed.
Now, that it seems pretty much granted that the shinny new iPhone 4 has big antennas problems. I've decided to look into the details and real data.
I logged in on my AT&T and pulled the data from my wife calls log and extrapolated about the one that have potentially dropped. It was easy... I looked for communications with the same number around the same time. Then I went through the data with her to confirm. Here is the raw data:
So it looks like roughly 2/3 of the calls dropped. It's waaaay more than before we switched to the iPhone 4.
Now, I, and she, needs to decide if we're going to return the phones or not. The lack of clear acknowledgment for the problems from Apple is not really encouraging. I know, it's a tough issue, and I'm sure it's hell on earth at Cupertino. But we only have 30 days to return the phone, why should we take the risk to be stuck with a semi-working phone? My wife rely on that phone for business, she hates dropped calls. Why should we have faith on Apple to be fair and honest about resolving that problem, eventually (Remember Airport Express issues)?
What is your experience with this? Is 2/3 a wide spread number or is it high just because we were unlucky?
The first one sets basic networking up including the private ip that is asked upon image creation, the second one installs chef using gem.
once the linode is up you can track installation progress by 'tail'ing
You can automate further if you wish, like auto-validating the client but for obvious reason I wouldn't recommend to publish the stackscript publicly. Otherwise the next steps are to copy 'validation.pem' in /etc/chef/ and assign a role to the new machine. Then wait for chef-client to run or run it manually.