Powered by Jott

Coming home from San Francisco yesterday got a bit too adventurous for my tastes. We made it to the Powell Street BART station on time, but the train we had been planning to board was running late. I figured this wouldn’t be a problem, since we had allowed for a missed connection. Our second BART train was on time, so we pulled into the Richmond BART/Amtrak station right on schedule. The Capitol Corridor #746 was sitting right next to the BART tracks, separated from us only by a chain link fence. (The BART train was clearly visible to the Amtrak personnel, if they had bothered to look for it.) We had already arranged for Caitlin, the fastest of us, to run down the platform and stairs, under the tracks, and back up onto the Amtrak platform so she could hold the train for us. I’m sure that there is somebody on the planet who could have done this faster than Caitlin, but I don’t think any of them were traveling with us last night. Anyway, as you’ve probably guessed, Caitlin’s head was just clearing the top of the stairs when the doors closed and the train pulled out of the station. Nice way to handle a connection, Amtrak!

We had also planned for the possibility of missing this train. The last train of the day, #748, was due in exactly another hour. But I had never been in the Richmond station after dark, and the quantity and “quality” of beggars, weirdos, and other assorted lowlifes was an eye-opener. Also, it was getting chilly and the wind cuts through every bit of that station like a knife. (We had already spent an hour at the same station that morning. Colder, but no zombies out between 07:00-08:00 on Sunday morning.) So I’m stranded on Amtrak’s platform with my wife and three teen-aged girls, and it’s getting colder and darker by the minute. I could deal with being asked for spare change every few minutes, but the lady down in the station area screaming and cursing at her small children pushed my wife and I beyond our limit, and we decided to get out of there however we could.

Fortunately (?), we weren’t the only ones who got stranded by Amtrak. Two small groups of college students had been on the same BART train, heading for Davis via the #746. We approached both groups, a pair of young women and three young Chinese students, and asked if they would care to join us. Strength in numbers! Now instead of three frail groups, we were TEN–Don’t mess with Us! Granted it was two children, four young women, two young non-threatening guys, and a middle-aged couple, but we all felt much safer in each other’s company.

There was a Burger King about 1.5 blocks away, so we headed for it. Our bad luck continued, as they had locked up the Burger King dining room just before we walked up. (After our experience in that part of town, I can hardly blame them for their policy!) There was a grocery store in the same parking lot, and we managed to get in there before they closed. We agreed to meet back at the front of the store in time to walk back to the station, then we split up and bought ourselves some cold supper. We made it back to the station without incident, in plenty of time for the final train.

Two paragraphs back, I wrote “Fortunately (?)”–I think it was fortunate that we didn’t make that train, because I’m not at all sure what would have happened to those college students if we had made it and they hadn’t. Would they have banded together? Even if they had, would a group of five been enough for a deterrent? Thanks, Amtrak, for giving me some unpleasant mental fodder.

I may take Amtrak at some point in the future, but I don’t think I’ll ever again stop at the Richmond station. I’ll find another way to make the Amtrak/BART transfer, even if I have to walk a few blocks to do it. But I’d really like to know what the operator/driver/engineer was thinking when that train pulled out 30 seconds early, leaving 10 paid passengers stranded in a crappy part of town?

Powered by Jott

Powered by Jott

We’ve got some fun plans for this weekend, but I’d rather write about them after the fact. Besides, that way I can post pictures to go with the article!

M8R-3cqng3@mailin8r.com

Once this post has been online for a while, I’ll post the number of spams I’ve received at that address.

For those unfamiliar with Mailinator, it’s a slightly odd email service. There is no registration or password required (or even permitted!), so don’t use this for anything where even a hint of privacy is desired. Most people use this for disposable email addresses, e.g. for sites that require registration. See the Mailinator FAQ for more information.

Several people have been asking us about hosting, how we found out about this, etc. Our daughters took/are taking French at Rio Americano. Their teachers, M. Hodgins and Mme. Murray, are both involved with the VIE exchange program. M. Hodgins organizes the biannual trip to France, while Mme. Murray organizes hosting for French students every year. If any Sacramento-area residents are interested in hosting a French student during the summer (usually 3 weeks in August), contact Mme. Murray–she was only barely able to place all the students this summer, due to a shortage of host families!

We’ve got some trips planned for Caroline’s visit, although Mme. Murray tells us that some of the most interesting things for the visiting students are (from the host’s perspective) purely mundane: Things like going to the grocery store, making dinner, going to school, etc. (Yes indeed, Caroline gets to spend the final week of her visit going to Rio Americano with Caitlin. We’ll have to come up with some fun things to do in the evening to make up for that!)

If it stays on schedule, Caroline’s flight will arrive in six and a half days. Well… 6 days, 11 hours and 56 minutes, but who’s counting?

# cd /usr/ports/security/openssl-stable
# make clean
===>  Cleaning for openssl-stable-0.9.7m
# make
===>  Extracting for openssl-stable-0.9.7m
=> No MD5 checksum recorded for openssl-0.9.7m.tar.gz.
=> No SHA256 checksum recorded for openssl-0.9.7m.tar.gz.
=> No suitable checksum found for openssl-0.9.7m.tar.gz.
*** Error code 1
Stop in /usr/ports/security/openssl-stable.

The problem is caused by a recent change in openssl which deleted the checksum information for the stable version (0.9.7m) of openssl. The fix is pretty simple: just restore the checksum info for 0.9.7m to /usr/ports/security/openssl/distinfo. I’ve submitted a PR to the project which contains a patch file for folks who’d rather use patch(1) than copy-pasting three lines of text.

Hat tip to Andy for pointing this out to me. You da man!

I would have included a copy of the image, but Google’s T&C’s forbids it.