Find large files on a Mac using Terminal

Every few days, I had an issue where my startup disk was full and emptying the trash just wasn’t doing enough.

I found the following command online that searches a file system for files over 500MB and prints the file path. It identified files I had totally forgotten about as well as some huge files generated by apps I no longer used.

sudo find / -size +500000 -print

I then used the rm command to delete files. When deleting entire directories I used the recursive flag (be careful!)
rm -rf <directory path>

Kudos to davidcraddock.net

Mac OSX Shell Script to automate connecting to WiFi network

I have a Mac laptop running ‘Snow Leopard’ that occasionally will not connect to my home WiFi, even though other devices are connected to the network just fine.

I wrote a small shell script that uses the networksetup command to reset AirPort. If WiFi is still not connected, the script tries to assign the AirPort WiFi network directly. If that doesn’t work, it just resets AirPort again.
Continue reading “Mac OSX Shell Script to automate connecting to WiFi network”

Use a PuTTY generated key on Mac OSX

I wanted to use the key I generated using the PuTTYGen tool on my windows laptop, on my now repaired Mac Pro. The standard PuTTY generated key will not work on Linux or Mac OSX, so the key needs to be converted into a standard that will, like OpenSSH. You can convert your key by using the ‘Export to OpenSSH’ option explained in a previous post.

Once you have your new private OpenSSH key, copy it to your Mac.

Open terminal, and go to your root… usually does this automatically, but type cd ~/ just in case.

Create a .ssh directory if it does not already exist and copy the private key in here.

You may need to check that the key has the right permissions, type chmod -R g0-rx ~/.ssh

Enter your ssh command, ssh username@serverhostname.com and hit enter, you should get now have a SSH tunnel to your server.

HANDY TIP: use the vvv flag to debug the ssh command¬† (looks odd but thats 3 v’s by the way!).

So type ssh username@serverhostname.com -vvv to receive a load of debug info that can be really useful in determining where you are screwing up.

Also I found this guide useful.