When we lived in Japan we went to Tokyo Disney once, and to Universal Studios Japan several times. At Tokyo Disney, even though we went in the off-season on a school day, the wait times for most rides were over 60 minutes. At Universal Studios Japan (unless you purchase their “Express Pass Booklet” which allows you to go into a faster queue) we have seen wait times of 180 minutes for popular rides. We also went to Disney Paris a couple of times in January, snow and freezing rain tend to keep the visitor numbers down, so we did not have to wait at all for most rides. My expectations for Florida’s Disney world were wait times similar to Japan. I was very pleasantly surprised. The longest wait times we saw were 60 minutes, and for those rides that did have longer wait times, we got the “Fast Pass” and went back to them.

The flights were fine and we were able to get to the “All Star Music Resort” on the Disney coach fairly easily. Little did we realize that escape from Disney would be impossible for the next 7 days. This had us paying $14 for a six-pack of beer, and $2 for a bottle of water for the week. The $10 a day extra for a fridge in the room and $9.95 a day for internet access also made me feel that we were being gouged.

The food was better than I had expected. I had thought that we would be eating burgers and fries for a week, but there were delicious alternatives - the kids meals all came with a choice of 2 sides, Jessica usually chose carrot sticks to go along with her fries, and there were delicious salads available too.

Jessica loved the rides, especially the scarier, faster ones. Space Mountain 5 times, Thunder Mountain 4 times, Splash Mountain 3 times, Everest adventure 3 times, Tower of Terror 4 times, Fast Track twice and Mission: Space. Unfortunately she did not quite make the 48 inch height requirement for some of the water slides at Typhoon Lagoon.

I am glad to be back at work - now I do not have to walk miles every day in 90+ F temperatures Hopefully we can avoid theme parks for a couple of years.

Really though, some things have happened, I got work building pacakges
for The Written Word on a part
time basis. It’s fairly interesting.

My daughter is growing up, see some pictures at pic.pogma.com(slow!)

Oh, yeah, almost 2 years without smoking, not too bad. Now if only I
could stop gaining weight.

Well, that’s it for another year!

We’ll see if I can continue, I still spend a large amount of time thinking about smoking, but am able to concentrate
for more than 5 minutes at a time again (I couldn’t for a while, just kept thinking about how much I wanted to smoke).

WRONG!

I discovered today that it is indeed possible to call dl functions after exit() has been called.
C++ static destructors can be called after I do my cleaning in dlcompat_cleanup. So, exit calls dlcompat_cleanup which deallocates all it’s malloc’d blocks and the pthread locks etc. exit then proceeds to call
the c++ static destructors which call dlclose, at which point dlcompat barfs all kinds of ugly stuff before it dies rather vocally.

So now I guss I have to go patch dlcompat to leak again. Sometimes it is better to leak
than have something squat on your head and do a big poop.

On the downside, of course, is that I am now one of the people that patch submitters
are going to be mad at for not committing their patches as soon as they post them to the mailing list.
I used to think that it was a relatively easy process, but it is a little harder than
I originally thought.

Got to make sure the patch does what it says, try your best to ensure it breaks nothing,
and, of course, test the thing on as many systems as possible.

No wonder it took forever for my patches to be applied.

I hope I have fairly recent backups of the important stuff, although I’ve a
horrible feeling I’m missing my gpg key.

• Make -framework foo and -F/path work properly
• Update the documentation to reflect reality
• Change ltdl so it prefers the dyld code I added rather than any dlopen function it might find.

I don’t think I’ve said this enough, libtool is a pain.

The MD5 Sum for this disk image is: 99bfaac4fec5fc96ed11f7724b8d3c1a

There are build instructions included on the disk image, but do not rely
on them being easy to follow.

I have yet to figure out why it is necessary to patch Qt, it seems likely
that it is a MySqlCC bug.