Here’s the magic, just pump this into your terminal, restart Safari and you’ll be ready to go:
defaults write com.apple.Safari TargetedClicksCreateTabs -bool true

After trying to convince various AppleScripts to make iTunes clean itself up, I stumbled across these instructions on the blog of Todd George on how to find and remove byte-for-byte duplicates from iTunes. It saved my sanity. Note that this simply removes the files from the filesystem, and not the entries from the iTunes library itself. Thankfully, Todd provides a link to a great method of finding the now dead entries in your library and removing them WITHOUT any additional scripts or programs.

iTunes is happy again!

I found the following command works until Apple fixes the bug. Next time, I’ll also try using Disk Utility (thanks to the guys on Apple support forums for both tips).

Open up a terminal, cd to /Volumes, get the name of a mounted DMG file, and try like this:

(in my case the volume was /MailTags2.2b4):

maggie:Volumes blloyd$ hdiutil detach MailTags2.2b4
“disk1″ unmounted.
“disk1″ ejected.

Link to specific message

Unfortunately, the article doesn't take the user beyond using CVS at the command line. Ideally, you'll want to connect to your CVS repository using a much more flexible GUI tool. I forcibly recommend using Eclipse. The integration of CVS directly into an IDE has been a long time coming, but I can't give it up now that it's here.

There is, however, a trick to getting Eclipse to connect to the localhost repository. Enter the System Preferences menu by clicking [Apple] in the top left and selecting "System Preferences". Now select "Sharing" from the "Internet & Network" area. Under the "Services" tab, select "Remote Login" and press the start button.
Warning: Not only will you be able to SSH into your own machine, but anyone else with your password can as well. Enable Remote Login at your own risk. Check out this article over at Mac Geekery called Basic OSX Security for more information on securing your Mac.

Once you've enabled Remote Login, you can test it by going to the Terminal and typing ssh localhost. You should be prompted for your password, and should get a welcome message if you enter it correctly. Type exit to return. Congratulations, SSH is working!

The final step is to commit your Eclipse project to your newly created CVS tree. Now you can do this from the command line, but it's even easier in Eclipse.

With your project open, right click on the project folder and choose "Share Project" from the "Team" menu item. Remember the Team menu item, this is where all your CVS functionality will be once you've got your project set up.

Choose the "Create new repository location" option and click Next.

At this screen, you need to enter the location of the CVS repository you wish to commit to. The host should be "localhost" and the repository path should be "/usr/local/cvsrep" if you followed the setup tutorial to the letter. Change it to whatever values you are using. Make sure "extssh" is selected in the connection type drop down!

At the next screen, I usually select "Use project name as module name", but feel free to enter whatever you like. After you choose your module name, click Next.

Eclipse will then connect to the server and create the module. When it returns, it will confirm with you the files that it will be committing in. Clicking Finish will finally bring up the Commit wizard which allows you to enter some text for a log entry. Something like "Initial check in" usually works great.

You should now be in Eclipse-y version control heaven! Enjoy the good life and happy committing!

Of course, now that you've switched your personal machine, you probably feel motivated to spread the wealth to your friends and family. Alternatively, you're like me and you're sick of having to fix those old PC that belong to your friends and family. Stick with the spread the wealth one, trust me.

Here's how to approach switching all those other computer users in your life. Hell, it might even help make your own hypothetical transition a little more managable.

Step One: Be proactive – Start switching to cross platform applications NOW!
A year ago, I switched my parents from IE and Netscape Communicator to Firefox and Thunderbird for one reason: Sanity. IE virtually guarenteed that my parents computer would be so bogged down with spyware that the only fix was a fresh install of Windows 98. Then I'd have to scramble to find a copy of Netscape 4.75 so that I could get my Dad's main back to how he liked it.Little did I know, I was setting my parents up for an easy transition when it came time to replace the old Dell with a brand new Mac a year later. Their relationship with the computer revolved mostly around email and internet. Thus during the transition from Dell to Mac, the two most used applications on the computer didn't even change. All the bookmarks, addresses and old email transfered across in a matter of minutes. Your milage may vary of course, but the lesson is simple: Take an inventory of the most used applications and try to find cross platform alternatives. Firefox/Thunderbird are no brainers. They're both free and very capable, and Internet and Mail are going to be high up on the list. Word processing is a bit more compliated. Although there is a free, cross platform solution available, it isn't exactly light weight and lacks some of the user friendliness. If you unsuspecting switcher is an Office user, get them to bite the bullet and get a copy of Office for Mac.

Step Two: Buy peripherals with cross platform driver support
This isn't as much of an issue as it used to be and really is just an extension of step one. I've been very impressed with the driver support of my Macs so far. All the printers that I've plugged in have printed without any complaint (or indication for that matter). When I switched my parents, I lucked out. Both their HP printer and Epson scanner worked like a charm. If you have to purchase a peripheral like this before you make the switch, double check that you have the option to hook it up to a Mac.

Step Three: Don't force the issue
My Dad bought my Mom a brand new digital camera for Christmas. When I came home for Christmas he asked me to set it up on their ancient Dell. I know from experience that Windows 98 is not exactly the friendliest experience for the digital photographer. Windows XP would have worked resonably well, but I was very impressed with my experience using iPhoto. I knew my parents would agree.The point is that there's no reason to force a Mac on someone who's not interested or ready to receive it.

Step Four: Buy for fit
Buying a Mac is like buying a suit. Make sure it's a comfortable fit. Don't sacrifice just to save money. If your switchee ends up with a low end Mac and doesn't like the experience because the hardware is limiting, they're going to blame the experience on the Mac rather than their configuration. We took a look at the Macs and decided the while the 17" iMac was more than enough machine, it was also a lot more likely to stand the test of time. The large harddrive, DVD burner and extra RAM meant that it will be capable for a few more years. Your milage may vary.

Step Five: Buy them a book
There are all sorts of books available as an introduction to OSX ranging from extreme beginner to power user. As a "Welcome" gift, buy a book for your switchee. Not only will you help them discover new things about their new Mac, but you'll save yourself some time answering questions and give them a sense of independance.