Send files to your trash in OS X from the command line

So yesterday I wrote a little Objective C tool that behaves like `rm` but instead sends the files or directories to your Trash using Finder. The code is available at [samuelkadolph/trash]( You can clone that repo and run `make install` or if you have homebrew you can run this:

brew install

PhidgetSBC2 and D-Link DWA-160

So I’ve had a little project going on with the foosball table at work: a system to detect when someone scores a goal. I’ve built a prototype photogate that goes inside of the goal. My design is to have 2 photogates hooked up to my [PhidgetSBC2]( and write some ruby code to detect a goal and send a message to a connected iPad app to indicate who scored. Everything was going fine until I took the PhidgetSBC2 to our foosball table and discovered our 2.4GHz network had no coverage there. Which means the [wifi usb adapter]( I had for the PhidgetSBC2 was useless. Undeterred I started on 2 different solutions.

Continue reading “PhidgetSBC2 and D-Link DWA-160”

PhidgetSBC2 and ruby

Installing ruby (and the [`phidgets-ffi`][0] gem) on the [PhidgetSBC2][1] is fairly simple. You will need to check `Include full Debian Package Repository` under `System > Packages` in the SBC admin page. And then just ssh into the server and run the following:

apt-get update && apt-get install ruby1.9.1 ruby1.9.1-dev build-essential -y

And then you can install the [`phidgets-ffi`][0] gem like so:

gem1.9.1 install ffi phidgets-ffi

The gem doesn’t find the `` on the [PhidgetSBC][1], so we need to symlink it to somewhere that the gem will find it.

ln -s /usr/lib/ /usr/lib/

Once we’re done this we can test it with this:

ruby1.9.1 -rphidgets-ffi -e ‘puts Phidgets::FFI.library_version’

I also like to run this to add the `ruby1.9.1` executables (i.e. `rake`, `irb`, `gem`) without the `1.9.1` suffix.

update-alternatives –install /usr/bin/ruby ruby /usr/bin/ruby1.9.1 400 \
–slave /usr/bin/erb erb /usr/bin/erb1.9.1 \
–slave /usr/bin/gem gem /usr/bin/gem1.9.1 \
–slave /usr/bin/rake rake /usr/bin/rake1.9.1 \
–slave /usr/bin/testrb testrb /usr/bin/testrb1.9.1 \
–slave /usr/bin/rdoc rdoc /usr/bin/rdoc1.9.1 \
–slave /usr/bin/irb irb /usr/bin/irb1.9.1

I also like to create an `.gemrc` to skip installing `ri` and `rdoc` documentation to save on space.

echo install: –no-rdoc –no-ri >> ~/.gemrc
echo update: –no-rdoc –no-ri >> ~/.gemrc


StartSSL cert with mumble-server on Ubuntu 12.04

With the release of Ubuntu 12.04 I decided to upgrade the server running my mumble server and I wanted to use my new wildcard certificate so my mumble server would have a nice shiny green background. All went well with my upgrade to 12.04 and getting nginx to use my certificate was easy. Next was to add my certificate to mumble and then I ran into a problem. No matter what certificates I provided to the config (sslCert and sslCA) I would always get his error when a client tried to connect.

1 => <1:(-1)> New connection: XXX.XXX.XXX.XXX:XXXXX
1 => <1:(-1)> SSL Error: No certificates could be verified
1 => <1:(-1)> Connection closed: [-1]

Long story short: I added the ca-bundle.pem from StartSSL to /etc/ssl/certs and then it all worked.

Simple Rails Multi-Tenancy II

I suppose it’s about time I updated my [Simple Rails Multi-Tenancy]( post to use the latest rails [3.1.1]( Not much has changed from the 3.0 beta to 3.1.1 in terms of the method I use to achieve multi-tenancy but the code has become a bit cleaner (but the patch required is a bit larger). This time around I’ll skip the commands and just go straight to the code itself.

Continue reading “Simple Rails Multi-Tenancy II”

Faking an iOS Framework

Ever wanted to share your iOS code with others without having them copy your code and headers and hope it compiles properly? Well you can easily do that with frameworks. I had found several guides on how to do this but they were either out-of-date or incomplete. While the iOS App Store doesn’t allow you include dynamic frameworks, you can create a relocatable static framework which functions very simliar with one key difference (more on this later). One more thing we can do to simplify distribution is to create a universal framework so that they same file works on the iOS device (`armv7`) and in the simulator (`i386`).

Let’s get started by creating a new project in Xcode.

Continue reading “Faking an iOS Framework”

jruby with 1.9 mode as the default with rvm

Thanks to [recent commits](…2388c1af) from [Wayne](, you can now pass a build flag when install jruby with rvm and it will build jruby instead of downloading a prebuilt copy. Make sure you `rvm get head && rvm reload` first. Then we can install jruby with 1.9 mode as the default:

rvm install jruby -C -Djruby.default.ruby.version=1.9

And if you want to use jruby-head:

rvm install jruby-head -C -Djruby.default.ruby.version=1.9

Cocoa Entitlements and EXC_BAD_INSTRUCTION

So I’ve been playing around with Lion sandboxing and using entitlements for a Cocoa app. *(In case you didn’t hear, all apps submitted to the App Store have to be sandboxed come this November.)* The first thing you may notice when you enable sandboxing for your app in Xcode is that it turns on code signing. It has to do this because entitlements don’t work unless you sign your code. Once code signing is turned on and you try to compile you may get an error:

[BEROR]Code Sign error: The identity ‘3rd Party Mac Developer Application’ doesn’t match any valid certificate/private key pair in the default keychain

This because by default Xcode will try to sign your code with an identity in your keychain that starts with `3rd Party Mac Developer Application`. To be able to submit apps to the App Store you have to get a certificate from Apple so this is a sane default but I wasn’t signed up of the [Mac Developer Program]( I was however signed up for the [iOS Developer Program]( so to fix the error for now I changed the `Code Signing Identity` build setting to `iPhone Developer` and away I went.

Fast forward a few days after I had signed up for the Mac Developer Program and I got my certificate. So I got rid of my change `Code Signing Identity` and restored the default. But I soon ran into a problem, my application now crashed while starting up no matter what I changed with a `EXC_BAD_INSTRUCTION` error in some random Apple code.

I quickly localized the problems to having entitlements on but the non-existance of any documentation on debugging sandbox errors from Apple I was frustrated. So I fired up my application without Xcode so there would be a error trace I could view in [Console]( This was a great idea because I was actually able to see what was the error was.

What immediately jumped out at me was

Code identity not in ACL for container ~/Library/Containers/org.samuelkadolph.Foo/Data

and I suddenly remembered something I read in the [sandbox documentation]( By default in the Lion sandbox, you can only access files in a special directory under `~/Library/Containers` which is named after the bundle identifier for your app. And it’s protected to prevent someone from accessing the data in there with a fake app. This protection is achieved by using info from the app which was signed by your code signing identity to confirm a genuine app from a fake. So when I changed the keychain identity used to sign the code I was creating a fake app and trying to access the data.

The solution was simple after determining that was the problem. Just delete the container for your app (**and only your app, every other sandboxed app has a container too and may store data in them**). In my case it was `rm -rf ~/Library/Containers/org.samuelkadolph.Foo`.

It’s unfortunate that Xcode isn’t more helpful with this error and unfortunate that OS X will kill (*with SIGKILL too*) an application instead of using some error handling in the app itself. I hope this post helps you if you ever run into this problem.

Parsing Proxy Auto-Config files

One thing I’ve always been wanting to be able to do was parse a [proxy auto-config]( file from the command line.

I only recently found the [pacparser]( library but found it limiting because it isn’t easy to install and use. So I decided to write a rubygem that would parse a pac file.

I started using the [`execjs` gem]( but one thing I quickly figured out is that you cannot implement all of the pac functions in pure JavaScript. Most notably is the `dnsResolve(host)` function which you cannot write in JavaScript because it lacks a way to make DNS queries.

So I took the code from execjs that deals with the four native runtimes and modified it to make ruby methods available in the JavaScript runtime. And now it’s available in the [`pac` gem](

You will need a JavaScript runtime installed to be able to use the `pac` gem, I recommend [`therubyracer`]( gem for ruby and [`therubyrhino`]( for jruby. [`johnson`]( only works with ruby 1.8 and [`mustang`]( requires the `v8` library to be installed.

gem install therubyracer pac

And now you can use the `parsepac` executable.


Or in ruby.

require “rubygems”
require “pac”

pac = PAC.load(“”)
pac.find(“”) # => “DIRECT”

pac =“sample.pac”)

pac = PAC.source <<-JS function FindProxyForURL(url, host) { return "DIRECT"; } JS

Introducing TrueCrypt Mounter for OS X

After playing around with using TrueCrypt and syncing the volume over Dropbox I was disappointed to discover that it doesn’t let you mount the volume by double clicking on the file. You have to open TrueCrypt, select the file and then type in your password.

To further expand my knowledge of OS X application bundles I set out to write an application that associated with the `.tc` file extension and when you opened a `.tc` file it would prompt your for your password and once you are done and eject the disk, automatically dismount the TrueCrypt volume.

The fruit of my labour is available in [this GitHub repository]( and you can download [the application here](
Once you have copied the application to your `Applications` directory, it will associate with any `*.tc` file. You must add this extension to any of your TrueCrypt volumes because (unfortunately) TrueCrypt does not do this for you automatically.