Take a look at the domain name. Combine that with one of my personal mottos: "Work hard, play hard". You now have a pretty good picture of my Thanksgiving!

Here's the short list:

• Dislocated shoulder (right side)
• Hyperextended knee (right side)
• Dislocated hip (right side)
• Massive swelling/bruising of knee (right side)
• Bloody cleat marks on the face

Let me explain.

Turkey Bowl

I'm not sure if this is a tradition in your parts but we keep it alive and well in the family. Things get even more interesting when family is involved in the actual game. We had just such a Turkey Bowl game this year: a perfect storm involving 3 brothers-in-law and a bunch of former high school team mates.

I won't give you a blow-by-blow but the highlights are necessary. First, we were playing full-on tackle football. It's like two-hand touch without holding back, somewhat akin to Rugby (in case you were wondering). Alex (one of the brothers-in-law) setup a game at a local high school stadium, called a few former team mates from the football team, and we got cracking. It was a good set- solid quarterbacks, receivers, and even a couple of linemen. All-in-all, a good setup for a great game.

A great game it was- I was on the team opposing both Jesse (brother-in-law) and Alex (the other brother-in-law). This was both fortunate and unfortunate: Jesse and I have an ongoing rivalry. I've challenged him to a wrestling match this year- one in which I intend to beat him soundly. He's an excellent wrestler, outstanding athlete and all-around great guy. Still, he's a superb target: 6'7", 220 lbs., lean, extremely strong, and a highly skilled wrestler. You can't make it any more of a stretch for a 170 lb., 6'1" scrawny whelp like myself.

I choose to guard Jesse. He's a fast mover but, due to the physics, has a harder time accelerating than I do. I didn't think this was a concern until:

Ouch.

Jesse was on a roll. Checkout the bulldog takedown:

Then it was my turn. I can't emphasize enough how glad I am that my wife took these shots:

If you can't tell, the little person tangled up in Jesse's legs is me. And yes, he's about to go down - hard.

In the end, Jesse, Alex, and Ben (all on the opposite team) won- by a single point. But, thanks largely to my efforts, they paid dearly for every point. I made several tackles, scored one touch down, and kept Jesse from getting more than that.

Unfortunately for me, I also paid for my heroic efforts. Toward the end of the game, I made a very poorly aimed tackle- throwing my arm in the path of the receiver's legs. It's not a strategy I would recommend and not one I would take, had I been in pads. To be honest, I wasn't sure if I would be able to take him down. This indecisiveness and poor execution left my arm out of the socket and me writhing in pain on the ground. With cleat marks on my face, just to salt the wound.

There wasn't anything for it but to get back up and play out the game. Still, to this day, my right arm is only semi-functional. It is, after all, quite painful to dislocate a shoulder.

Wall Walking - or Plain Idiocy

I don't think anyone would be embarrassed by an injury obtained in a tackle turkey bowl game. I wish that had been the source of the rest of the damage. Alas, it simply isn't so. If you refer to the list above, you'll note that the following remain:

• Hyperextended knee (right side)
• Dislocated hip (right side)
• Massive swelling/bruising of knee (right side)

I could spin some heroic tale to justify these injuries - I frequently rescue babies in strollers from drunk drivers, after all - but there wasn't anything glamorous in the true origin of these particular ailments. In a sentence:

I tried to take a large step up an unstable rock wall and slipped.

That's it. That's all it was. That single step hyperextended my knee, pulled my leg almost clean out of the hip socket, and gave me a worrisome, swollen, disfiguring bruise just below the knee. To top it all off, that knee is still giving me trouble when standing and walking, let alone while running.

It's frustrating to realize the price of stupidity. Remember that.

Wrapping Up

(That was a pun, by the way!)

This blog is not for the faint of heart. There's a mix of geekery, athletics, and, above all, living life to the fullest. The by-product of the latter is described in the domain: Accident Prone. For those who dabble in the sedentary lifestyle, I would tell you this: the scars are better than photographs for reminding you of the thrill of living. The pain fades with time and, with enough experience under your belt, pain itself can be little more than a distraction to the life you're living. Get out there and give it a try.

(That has to be the weakest and least effective invitation evar. Still, I recommend it.)

ESXi 5.0 was released a shot while ago. I run a small datacenter in my basement, some of which is virtualized using ESXi. The hardware is unfortunately a bit dated and has never been officially supported by VMware so, needless to say, some customizations are in order. For those struggling with old hardware and incomplete documentation, here's a bit of help.

VIB? Do I need that?

ESXi 5.0 introduces a new concept for packaging and installing third-party drivers (among other things): VIBs. You can read a bit more about them here. I won't go into the details except to say that, for the most part, you probably won't be creating your own. I spent quite a bit of time exploring that option only to finally resolve that it simply wasn't the right approach for me.

The reason behind this is simple: I don't actually need to install a new driver, I just need ESXi to recognize the older hardware as supported by existing drivers. To this end, after much searching, I found this article, which forms the foundation of everything you'll see here. The author had a similar problem- hardware going unrecognized by drivers that otherwise would have offered full support. His suggestion was to modify the existing driver packages and add the relevant entries to the driver's map file. Ingenious!

So how is it done?

If you've tried to follow along with the above article's suggested steps, you'll hit a serious snag: you can't unpack the driver packages with tar. You'll get an "Invalid tar magic" error, among other things. The extracted files also will not be usable. If you try and transfer it to a different host and unpack it, you'll notice that tar complains loudly about corruption and, to end it all, the extracted files are unusable. In short, DON'T TRY IT.

With that said, the approach is solid. After a bit more research, I discovered that the driver packages are actually vmtar archives, not vanilla tar archives. You can convert these to standard tar files with a simple command:

vmtar -x [file] -o [output.tar]

With that done, you can use tar to extract the archive, make any necessary changes (or additions), then tar it back up and use the following vmtar command to get it into the necessary VGZ format:

vmtar -c [file.tar] -o [output.vgz]

The specifics

In my case, I have an old SB600 SATA controller built-in to the motherboard that I would very much like to use. First step in the process is identifying it using lspci:

lspci -v

You'll get some output like this:

You can see my particular controller on the first line. Below, you can also see the PCI class association ("Class: 0106: 1002:4380"). The latter set ("1002:4380") is used to map the device to a driver in a standard linux distro's standard.map file. In the case of ESXi, these maps are driver-specific, supplied in the VGZ packages we've discussed. Once you've identified the hardware using lspci, the next step is to map the class declaration to a driver. Here's how I did it:

Since my example deals with a SATA AHCI controller, I looked in the /bootbank folder for a corresponding driver package. I found "sata-ahc.v00". To make the necessary change, I did as the article referenced above suggests:

1. cd /tmp
2. mkdir tweak
3. cd tweak
4. vmtar -x /bootbank/sata-ahc.v00 -o sata-ahc.tar
5. tar xvf sata-ahc.tar

Now I had both the etc and usr directories, provided by the driver package, in the /tmp/tweak folder- available for me to change! Note that I used vmtar first- this is the step overlooked in the original article. Next, I opened the etc/vmware/driver.map.d/ahci.map using vi and added the following line:

regtype=linux,bus=pci,id=1002:4380 0000:0000,driver=ahci,class=storage

Finally, I closed up shop and re-packaged everything using the following steps:

1. rm sata-ahc.tar
2. tar cvf sata-ahc.tar etc usr
3. vmtar -c sata-ahc.tar -o sata-ahc.vgz
4. mv sata-ahc.vgz /bootbank/sata-ahc.v00

Last step: reboot

That's it. The ESXi host came alive, the storage device was recognized, and I was on my way.

This is a pretty easy way to get new drivers on your ESXi host without having to create a VIB (which can be lengthy). You can add your specific driver file (compiled for ESXi) to the usr folder, add the map declaration as indicated above, vmtar it up, and go on your way.

Good luck- ping me with questions!

As you no doubt are aware, my family consists of 2 adults (well, at least one responsible adult and another that looks like one) and 5 children. Scroll down a bit to get a refresher course on the family (with pictures!). Feel free to jump down there now.

Back? You'll remember that our 5 children are ages 7 and down. This presents some unique challenges when the family chooses to do something like hiking, especially when that hike is somewhat challenging. This, as you'll have guessed, is precisely what we decided to do with our 4th of July: a bit of family hiking.

I won't disparage those sadly deluded persons who think that the pinacle of the outdoors is a well-maintained asphalt path that spans a completely level stretch between the parking lot and a small waterfall visible from the road (here's to you, Bridal Veil Falls!). Suffice it to say that we like the challenge and the beauty of the mountains, preferably away from the rest of human civilization. Given that we have 5 children, it isn't strictly possible for us to galavant around the raw wilderness, so we settled for a decent middle ground: the Aspen Grove Timpanogos Summit trail.

That trail is a tough route, if you follow it all the way to the summit. This time of year, it's not only physically demanding, it's extremely technical. We obviously didn't summit with 5 kids ages 7 and under; we simply went to the lower waterfall that sits below the first steppe on the approach to Emerald Lake.

Having taken young kids hiking before, we knew that this would be a pretty slow approach and, as we contemplated this, Elise and I came up with an idea to help us kill time on the way: give every child a digital camera.

The Setup

To be fair, we weren't exactly sure what would happen if we gave cameras to kids ranging from 2 to 7 years old (sorry, 11 months is a little young for this). We actually didn't have 6 cameras to go around. Instead, we scrounged my old iPhone (2G), our nice camera (Kodak Z712), and two iPhone 4s (mine and Elise's). Initially, we gave the iPhone 2G to Gini, my iPhone 4 to Thomas, and Elise's iPhone 4 to William. I kept the Kodak.

The Rules

Since we didn't have enough cameras for everyone, we setup a sharing regime- when we felt like someone had had enough time, we asked them to pass it along. This went surprisingly well and there are pictures from each of the cameras taken from every child (minus Jonathan).

We told the kids to take pictures of anything they found interesting- things that were different or unique, including plants, animals, and the like. We also asked them to take pictures of the family. Beyond that, we let them run loose.

The Experience

Of course, there are several pictures of plants right outside the van where we parked and there are a number of pictures from the first quarter mile of trail. Every so often, we would have to tell the children to "Lock the phone and keep walking!", though it was less prominent than you might think. The pace we set was pretty comfortable.

After the first quarter mile or so, the kids got down to business. Every 30 seconds or so, they would take a camera out of their pocket and snap a shot at something they found interesting. We tried to keep sharing up, but Thomas and Gini accounted for the bulk of the photos taken by kids. William took his fair share, Peter took just a few.

When they had settled into a rhythm of walking, snapping a picture, and returning to a walk, we made pretty good headway on the trail. There were a few fun spots: we crossed a raging stream on a wet and rickety bridge and we spanned a couple of fairly long and treacherous sections of snow. Of course, these were picture-worthy and we gave opportunity for both the kids and ourselves to take pictures.

Overall, the hike was fun and successful. The kids were in surprisingly good shape by the end. As you'll see in the album below, even our 2-year-old Peter was running and giggling at the end. As a hike and a family activity, it was fantastic.

The Results

What about the pictures? You just had to ask. We uploaded most of the pictures to Google last night and this morning, just to let you see how things went. For the most part, I think they're what we all expect: a few out of focus pictures, many pictures of nothing in particular, and a few beautiful gems. Those gems and the wonderful experience we had gathering them made this one of the best family hikes - and even general activities - we've ever had.

You can view the entire album with all of the pictures (unedited!) here:

Timp Independence Experiment Photos

Here's a simple slideshow for those who want to simply kick back and see what happened:

The Family: A Refresher Course

Just in case the names and ages are foreign to you, here's a quick refresher on the family (as it stands today):

Gini (Virginia), 7 years old	Thomas, 6 years old
William (Will), 4 years old	Peter, 2 years old
Jonathan, 11 months old

The two adults (one adult aged, one adult in truth):

Elise: The beautiful adult	Me: Adult-aged

Welcome back from the break. Memorial day is an excellent holiday in so many ways- remembering the fallen, teaching children the value and cost of freedom, and taking a Monday back from the work week.

This morning, I did something odd: I chose not to go to the gym. My normal schedule, which I've followed almost perfectly for the past four and a half months, is:

• 4:30AM: Wake up
• 5:00AM: Shower, dress, and head out the door
• 5:45AM: Gym (plus a swim on alternate days)
• 7:00AM: Commute (yay!)
• 7:30AM: Work
• 4:30PM: Commute (homeward!!)
• 7:30PM: Run, bike

...and it goes on. There have been a couple of occasions when I've even been out of town and stopped at the gym at 11:00PM before flying home at 6:00AM the next day... and headed to the gym at lunch, just to ensure I've gone every single day.

So why didn't I go this morning? Post-Memorial Day laziness? Nah, I still got up at 4:30AM (it's hard not to these days). The real point is a restructuring of exercise. I've got a few big events coming up over the next two months and, as much as I hate to say it, it's time for a change.

First things first, I've nearly doubled my lifting capacity over the past 4 months in practically every way. Take this with a grain of salt: I wasn't that strong to begin with. Still, 4 months is a short window for this kind of personal improvement. The point was to build the base of strength I've been missing over the past few years. And, of course, to attempt to gain the strength needed for me (170 pounds, 6 foot nothin') to successfully wrestle (collegiate style) my brother-in-law, Jesse (235 pounds, 6'7").

There's been an informal rivalry ever since I married into the family- I've wrestled (freestyle, folk, greco-roman, and collegiate) since I was 6 years old. My wife's family is equally entrenched in the wrestling world. I helped coach her younger brother, Theo, when he attended the high school I graduated from. When in high school, I had always looked up to her older brother, Jesse. Both of her brothers are amazing wrestlers. Jesse, in particular, is an amazing wrestler with an equally amazing physique. Let's just say that one look is enough to convince most rational people to not start something.

Earlier this year, I issued a challenge to Jesse: a 6-minute (3 2-minute periods), collegiate-judged, officially refereed, wrestling match, to be held in June or July at a local high school. I was going to try and beat him.

This challenge kicked off the heavy lifting campaign- I had to get strong enough to at least compete with Jesse on the mat. That doesn't mean I have to be as strong; I just have to be strong enough, enough to let technique, strategy and endurance make the difference. I set some goals- squat 400+, deep lunge 180+, bench 250+, etc.- all of which I've now accomplished. At the same time, I've tried desperately to maintain swimming, biking, and (more recently, due to injury) running, though these were de-prioritized in favor of building strength.

But now, 4 months later, the goals are satisfied and while I'm not strong enough, it's time to shift focus once again. The Wasatch Ragnar race is in three weeks, which forces me to re-prioritize running. I have several half-distance triathlons in July, August, September and October, along with several century rides I'd like to complete. We have a Mt. Rainier expedition in July. Above all, June is right around the corner and this epic face-off with Jesse is looming.

Thus the gym now becomes a 4 times per week event and I'll be reconsidering the muscle groupings I work per day. I'll be lifting to maintain and not gain. Running mileage will go up a fair bit, as will swimming and biking. I'll be adjusting these events as well- intervals will make a comeback for all three and I'll be alternating general speed work with stretching distance.

No sleeping in, for certain. I need to start running in the mornings, exchanging the time spent in the gym for time spent pounding pavement. What a marvelous zero-sum game we play with our time!

I'll be setting a date and time for the wrestling match. I'll even stream it, for anyone interested. It will be epic, however it turns out. Too bad this David can't throw stones...

Look for an announcement with a date. I'll post results for all events (wrestling, ragnar, triathlons, etc.) as soon as they're available. Enjoy the shortened work week!