To get to the SSH escape sequences, you need a new line, followed by ~ and ?. That’s a newline (return), followed by a tilde and a question mark. This is what you get

Supported escape sequences:
  ~.  - terminate connection (and any multiplexed sessions)
  ~B  - send a BREAK to the remote system
  ~C  - open a command line
  ~R  - Request rekey (SSH protocol 2 only)
  ~^Z - suspend ssh
  ~#  - list forwarded connections
  ~&  - background ssh (when waiting for connections to terminate)
  ~?  - this message
  ~~  - send the escape character by typing it twice
(Note that escapes are only recognized immediately after newline.)

There are a lot of interesting things you can do with this. My favorite being if you ssh to host1.cainmanor.com then ssh to host2.cainmanor.com and then ssh to host3.cainmanor.com and host3.cainmanor.com locks up, you can newline ~~~. and the third session will be closed.

But wait!! There’s more

You can do some very nifty things in your ~/.ssh/config file. First, you’ve got to make sure you have very restrictive permissions on that file – 600 or bust.

Host nickname
Hostname host1.cainmanor.com
Port 22
User gcain
ForwardAgent yes

Host – put a nickname you want here. You can use a wild card (*), if you’d like the apply the changes to all servers (for instance, change the port for all your servers)
Hostname – DNS name (FQDN highly recommended) or IP address.
Port – Port
user – user name you want to log in with.

You can also use this with rsync, but I won’t go too far into it.
Before

rsync -avr --delete --exclude '.DS_Store'  /share/MD0_DATA/Video/ gcain@host1.cainmanor.com:/share/external/sdz1/Video/

After

rsync -avr --delete --exclude '.DS_Store'  /share/MD0_DATA/Video/ nickname:/share/external/sdz1/Video/

Not as clear as a shorter example, but I wanted to keep this around for myself.

Not all Macs that are capable of booting a 64 bit kernel will boot the 64 bit kernel. The Mini is one of those… (This is from Apple.) Getting those machines NOT on the list to boot into a 64 bit kernel is possible, but it’s beyond the scope of this article (it involves editing your boot.efi.)

First, make sure your Mac can support 64 bits. Make sure your server is on the list above too.

ioreg -l -p IODeviceTree | grep firmware-abi

If you are 64 bit capable, you’ll see the following.

| |   "firmware-abi" = <"EFI64">

There are several methods. The easiest method is to hold the 6 and the 4 key when booting. This isn’t permanent, but the following are.

As root, type…

nvram boot-args="arch=x86_64"

To change it back to the default

nvram boot-args=""

I didn’t like this particular method, as I prefer to have a verbose boot

sudo nvram boot-args="-v"

There is one more way, that some people have had more success with. It involves editing /Library/Preferences/SystemConfiguration/com.apple.Boot.plist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Kernel</key>
	<string>mach_kernel</string>
	<key>Kernel Flags</key>
	<string></string>
</dict>
</plist>

You need to replace the null value below Kernel Flags () with “arch=x86_64″. The correct version -

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
        <key>Kernel</key>
        <string>mach_kernel</string>
        <key>Kernel Flags</key>
        <string>arch=x86_64</string>
</dict>
</plist>

To check if you’re 64 bit or not, you can use

uname -a

If you see

x86_64

You’ve got a 64 bit kernel.

This also works

system_profiler | grep "64-bit Kernel and Extensions"
      64-bit Kernel and Extensions: Yes

cat /tmp/blah | tr '[A-Z]' '[a-z]'

and to convert from lower case to upper case

cat /tmp/blah | tr '[a-z]' '[A-Z]'

When in an open/save dialog box, you can drag a folder into the dialog box to change to that directory.