The things you end up teaching yourself

One of the applications to which we were introduced at the NEH Institute on Networks and Networking in the Humanities — which goes by the hash tag nethums by the way — was a Carnegie-Mellon application called ORA. It and its companion application, AutoMap, are very useful tools for network analysis and visualization.

My difficulty with the applications was simply in getting them to run on my MacBook Pro. The problem was, is, that ORA, AutoMap, and their installers require an older version of Java than is included with Mac OS 10.6. With 10.6, Apple dropped the versions of Java 1.4 and 1.5 that they had been carrying and only provided 1.6. Java 1.4 is still available, but navigating Oracle’s site to get it, and getting it onto my MacBook was a longer road than I wanted to travel.

Now that I am back home, I got the good word that ORA had been updated. Great news! I headed over to the site only to learn that the Windows and Linux versions had been updated to version 2.2.2 but the Mac was still back at 1.6.9.


Two routes now lay open to me, if I wanted to run one of the newer versions on my Mac:

  1. Pick up a copy of VMWare Fusion or Parallels and run either Windows or Linux in a virtual machine, or
  2. Determine if there was a way to run the Linux application on Mac OS X (which is also a certified *nix now).

I had just spent a fair amount of money on corpus linguistics text — I’m working on refining a notion of “corpus folkloristics” — and so the idea of spending more money on virtualization software as well as for a copy of Windows is less than appealing. (I am already about to buy a copy of Windows 7 for our home desktop, but Microsoft offers now family pack the way Apple does, and so multiple copies of Windows is a little out of my price range for now.)

So, let’s go with the second option: run Linux apps on my Mac.

A page on Simple Help promised me a complete walkthrough of the process, the first step of which is getting Fink on my MacBook. (I had been using MacPorts before upgrading to 10.6, but the upgrade had broken it and so I was okay switching to Fink.)

Oops, no binary installer for 10.6. I was going to have to install it from source. Luckily, the Fink Project has a page up that walks you through installing from source. It does a pretty good job of getting you through everything, and it even tells you to run:


which would suggest to a command-line novice — I’m not quite a noob! — like me that, well, my path is going to be setup for me, which makes it all the more maddening when you enter:

fink selfupdate

and get the command not recognized response. Uh oh. And so I double-checked my PATH environment:

echo $PATH

and got all the usual suspects:


What’s going on? I closed the terminal and started doing some reading up on editing my PATH when I decided to double-check my work and ran fink selfupdate again. What do you know, it worked! Here’s the trick: I forgot to follow the directions and open a new terminal window after the initial installation.

And so I taught myself to follow directions.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.