I just uploaded the 617 pictures from our wedding phototgrapher. If you want to order any prints, please go to http://romanphotographyonline.com and enter the pertinent information - my new last name You can order directly from the photographer. But, in that process, I discovered that the new version (2.0.15) of FlickrExport for iPhoto is borked in a *very* annoying way. When I upload to both a set and a group photostream - it creates multiple sets - one for each photo. That means I have 616 extraneous sets on my Flickr account, and no way to delete them all at once. I have to go into each set one at a time and delete one set at a time - 616 times.

I’ve reported the bug, but it may take me quite a while to get around to deleting all those sets, and until the bug is fixed, I may not be uploading more honeymoon pictures. They’re not going to a group, so hopefully they won’t have that problem. Nevertheless, I’m going to only upload a few at a time.

Sorry to the maybe 3 readers of my weblog - I ran a portupgrade in FreeBSD over the weekend, and apache started core dumping for some reason - with absolutely no helpful information in the logs. I took advantage of this opportunity to upgrade to Apache 2.2.4. What I didn’t realize was how different my VirtualHosts configuration was going to have to be. At first, none of my virtual hosts were being recognized since I didn’t have the port on the servername. Then they were getting 403 Forbidden Errors because “Allow from all” is no longer the default - it has to be explicitly stated. It took me a while to figure that out.

But I’m back now, and the server may go up and down as I work on the SSL side and all the WebDAV folders I use to share things between home and work.

If you happen to notice any quirks, let me know and I’ll look into it.

From Magnio:

Xmas Stocking

leave a gift for elwing2000 your username: your gift: (30 characters or less) get your stocking

In the spirit of procrastination, I got up the nerve to upgrade my server yesterday. I went from FreeBSD 5.4 to FreeBSD 6.0 (and will soon go up to 6.2 when it’s released), from MySQL 4.1 to 5.0, and PHP 4.4 to PHP 5.2.

The system upgrade was less painful than the MySQL upgrade actually. I followed the excellent instructions at University of Colorado, and it worked flawlessly except for one issue. You know how he mentions the issue with older kernel modules being loaded into the 6.0 kernel? Yeah - I ran unexpectedly into that. I *had* the nvidia-driver port installed, and I looked in /boot/loader.conf to make sure that no others were going to be loaded, and booting into single-user mode isn’t a problem at all. Booting into multi-user is where the problem happened. /usr/local/etc/rc.d/rtc.sh loads the rtc driver - and it’s installed from ports. I just made the rc file non-executable and booted into multi-user just fine, then updated it via portupgrade -f.

The MySQL upgrade was fine on the server, but not so great on the client. I upgraded the client first with portupgrade, then the server. I had portupgrade recompile everything that depended on mysql-client (portupgrade -rRf mysql-client), so I thought I had gotten everything. I then stopped the server, and upgraded the server with portupgrade. Everything went fine until I rebooted for the system upgrade - then PHP stopped working. I recompiled *all* of php, and still no luck. So I figured, what the hell, I’ll upgrade to 5.0. The two things I need PHP for (my weblog and my gallery) would now work with PHP5 (they hadn’t at first), so I upgraded to PHP5. As soon as the php5-mysql extension was installed, everything was working fine. Other PHP extensions are still being installed as I write this, but the most important ones are there.