
I type this post through an Apple (wired) keyboard hooked to a 1st Gen MacBook. I’ve been severely disappointed in the quality of the MacBook (at least mine, anyway), when compared to the 5th Gen iMac I had before it. I’ve pretty quickly outgrown this machine. Given that later this month I graduate high school, I’ve managed to get my parents to agree in buying me a MacBook Pro for college (which starts in Fall).
Along with switching to a new computer comes data migration. How will I transfer everything over to the new one, and make sure that everything works? Given that I’m a developer, this is especially challenging because I have many things installed and configured just so. I need to get all of my music, photos, movies, and other media over to the MacBook Pro, while at the same time getting Apache configured, Django installed and configured, fighting to get MySQL installed, making sure I’ve got all Python libraries I’ve used in my apps installed,…the list just goes on.
I’ve decided pretty much to migrate as follows:
I have a 160GB external drive currently plugged into my MacBook when it’s at my desk. Of course I take my MacBook out with me, but when I’m at my desk, the external drive is there. I keep some files I don’t use much, but which are large, on the drive, and also share it over my network using SharePoints. I’ve chosen to transfer my files onto it, then plug it to the MacBook Pro and dump them onto the HD that way, rather than sending files over the network (which would go through the air at some point, and thus bottleneck at 54Mbps)
Transferring my media from iLife applications shouldn’t be too hard. I use the same username on all my machines, so the paths on the new machine should be mostly the same unless Apple changed something about the filesystem structure in Leopard (I’m still running Tiger). When I switched from the iMac to the MacBook all I had to do was copy the directories back to where they were. So the paths were still the same, and all the paths in the library files were still correct despite it being a completely different machine (for example, /Users/zacharytamas/Music/iTunes/) iTunes and iPhoto are about the only two iLife apps that I use that regularly enough that migration is that big of an issue. I don’t expect any problems when it comes to that.
However, migrating my development stuff is going to be very interesting. I’m at an advantage, however, as I’ll be starting with a completely new slate. I’ve had to do so much command-line tweaking and hacking to get things to work. When I first got the MacBook I was into Rails development, so I have the whole suite of Rails dev tools (Ruby, mySQL bindings for Ruby, etc.) installed alongside my Python/Django installation. Combined with a botched Apache2 and mod_python installation, I’m sure the underbody of my operating system looks an intertwined, ugly mess. Switching to Mac was the first time I had ever regularly used a UNIX based operating system, so I’ve had a lot of learning to do. This time around things should be much simpler, and more organized. Apart from a Leopard base install, all I really need to install and get working is mySQL and Django, and the bindings between them. I don’t even have to install Subversion now, thanks to Apple’s including it in Leopard. I shouldn’t have to upgrade Python this time around, either. Last time I had to install Python 2.5, and then recompile other related things and bindings to get my Django installation working as it should. I’m sure it’s all effed up, but it works.
However, I suppose I’m going to have to manually reinstall the Python extensions I’ve installed. I know better than to just copy my site-packages folder to the new system and expect it to work. Unless anyone knows a better way, I’m just going to install them as they’re asked for, hoping that eventually the apps I try to run stop throwing errors. There aren’t many that are absolutely necessary, anyhow.
</geek>
Whenever the MacBook Pro gets here I’m sure I’ll write about how it all ends up.