If you have SSH access to a UNIX/Linux based system somewhere and want to copy a file located on the server to your computer via SSH, you can use the scp command found in most UNIX/Linux systems, including Mac OS X.

Say you want to copy a file from the remote server to your own computer, a file called my_file.txt. In this case, you would issue the following command in your terminal:

scp your_login@addres.of.remote.server:my_file.txt .

This makes your computer connect to the server with the login you provide, and copy the my_file.txt file to the directory you are currently working (using the exact same file name locally on your computer, that’s why there is a dot in the end of the command).

If you’re running both Mac OS X and Windows 7, you might have encountered the problem of your USB key(s) either working on the Mac OS X or the Windows 7, and not on both of them.

Following the below guide will fix the problem:

Step 1) Partition the USB key using Disk Utility on Mac OS X. Make a single partition using the format “free space” and the partition scheme “Master Boot Record” (under Options).

Step 2) Insert the USB key in the Windows 7 machine. This will result in Windows 7 telling you that the key needs to be formatted. Ignore this message for now, and access Control Panel -> System and Security -> Create and format hard disk partitions (under Administrative Tools). Now, the Disk Management window should show up.

Step 3) You should be able to see the USB key here, possibly with the text being lined through. Right-click on the USB key tab and choose “New Simple Volume…”. Then, choose to use the entire disk, choose FAT32, choose to use the standard allocation size and then, choose an appropriate name for the USB key.

Now, all you need to do is finish the actual formatting and the USB key should work both on Mac OS X and Windows 7.

After having finished an update of your RubyGems installation, you might receive the following error:

uninitialized constant Gem::GemRunner (NameError)

If you get the above when trying to use gem, first of all, you need to find out which gem you’re using. Open up your shell and type in the following:

which gem

This will print out which gem you’re using and the location of it, typically being /usr/bin/gem or /usr/local/bin/gem.

Next, open up the actual gem file in your favourite text editor. If you’re using TextMate for Mac OS X, this can be accomplished directly from your shell by issuing the mate /usr/bin/gem command (you might need to change the path to gem to reflect your system setup).

Here, you’ll see a line reading require ‘rubygems’. Just below this line, add require ‘rubygems/gem_runner’, save the file and try to use gem again. It should work fine now. The change you need to do is shown below:

This showns the gem file brought up in TextMate. Line 10 is the fix.

If you ever experience a problem with importing vCards (.vcf files) that contain foreign characters in Address Book for Mac OS X, you might be in complete dark as to how to solve the problem with the foreign characters not being displayed properly.

You might have tried to save the vCard as ISO-8859-1, UTF-8 or the likes, and it still doesn’t work in Address Book. You might even have tried to add charset info in the MIME type of the vCard, having it display something like text/vcard; charset=iso-8859-1 all the while it still doesn’t work. Bugger.

The only solution is to make Address Book use a different character encoding for the vCards. If you access Address Book -> Settings… -> vCard, you’ll see the ability to change the character encoding. However, Address Book might have chosen vCard version 3.0 for you per default. Change this to 2.1, then change the character set to e.g. Windows Latin 1, and then change the version back to version 3.0.

Having done the above, the import of vCards containing foreign characters will work as expected. This includes vCards exported from Meeho!™.

A screenshot of the settings regarding vCards in Address Book.

(One last note: Having to choose vCard version 2.1 to change the character encoding, then changing the version back to 3.0 AND having Address Book preserve the encoding settings might be a bug… Seems odd that it preserves the encoding settings while jumping from version 2.1 to version 3.0, when the dropdown menu is dimmed when set to vCard version 3.0, indicating that a change is not possible in that case…)