Snow Leopard Chaos Subsides

Like a damn fool true fanboy I installed Apple’s Snow Leopard the day it came out. Sure, it was faster, and I liked the polishes they made to the user experience. But it broke a lot of things that made it possible for me to develop web sites on my laptop: MySQL, all my Perl modules, and the Ruby apps I use to track my To Do list (Tracks), and my projects (Redmine). I also lost the ability to print to my Canon laser printer, which I like cuz it does 2-sided printing. Also broken: Saft, iStatMenus, and Parallels, but I could get by without them (but did miss them).

Usually Google is my friend, but since it takes a few days for Google to catch up with people’s blog updates this time I turned to Twitter, and got up-to-the-second reports on people’s reactions to and fixes for Snow Leopard. MySQL turned out to be a quick fix, since it was just a broken symlink. After that my PHP scripts could once again connect to their databases, as could the Navicat app. But for the life of me I couldn’t get Perl’s DBI and DBD::mysql modules to work right, which meant a bunch of my older scripts weren’t working, and it made working on some of my older sites challenging in that I couldn’t test changes locally, I had to make them to the (gulp!) live site, which is hardly ever a good idea.

Every few days I’d search Twitter and Google for advice, and would try different things, but nothing would get Perl talking to the database :(

In the meantime I upgraded to Parallels 4.0 ($), which let me view my sites again under Internet Explorer. Since WinXP could still talk to the Canon printer I could print now if I saved to a PDF file, moved it over to Parallels and printed it there (ya, tedious, but at least it was possible). And new versions of iStatMenus (free!) and Saft ($) came out, so things were slowly returning to what we laughingly call normal here.

Labor Day (yesterday) was a down day that I used to finish digging the hole for the cob oven project (another post for another day), and I returned once again to my Perl/mySQL problem. Not a lot of people are using Perl anymore, or at least they’re not posting about their fixes for Snow Leopard, but all those hotshot Ruby kids kept saying they had to recompile the 64bit version of MySQL. Not wanting to break what was already working, I decided to try doing that on the family iMac and see if I could get Perl and MySQL working on it. Stock 64bit MySQL installed just fine, and I could talk to it over the command line. Good so far. I then installed the latest DBI and DBD::mysql modules using CPAN, which took a while but both installed with no problems (woohoo!). I created a small test table on the command line, then wrote a small Perl script to display all the records in it… and it worked!

Emboldened and embiggened, I then went over to the laptop, backed up all the mySQL databases, and removed all traces of mySQL from the computer. I then went thru the same steps as on the iMac; mySQL installed just fine, as did the DBI module, but DBD::mysql still refused to install. Desperate, I decided to copy the installed DBI and DBD::mysql modules from the iMac to the laptop, and after restarting Apache my perl scripts connected to mySQL just fine! Yes, it was a good day.

This morning for the heck of it I uninstalled all my Ruby Gems and reinstalled their 64bit versions, along with an updated passenger. After restarting Apache, Redmine once again started working! This is a very good thing, since I use it primarily as a GUI to the various Mercurial repositories I have for each of my web sites.

And a Google search for printer driver updates turned up a new driver which got my printer working again!

Jeezum, it’s like the morning of Aug 28, before I installed Snow Leopard! :)