Totally got me a hackintosh running.

From: About this Mac

Model Name:    Mac
Model Identifier:    Mac Pro
Processor Name:    Intel Core 2 Duo
Processor Speed:    2.13 GHz
Number Of Processors:    1
Total Number Of Cores:    2
L2 Cache:    2 MB
Memory:    2 GB
Bus Speed:    1.07 GHz
Boot ROM Version:    Hack.int.0sh

Wasn’t too hard to get running either, once I figured out what I was doing. I’m running an Asus P5B motherboard with a 2.13gig Intel Core 2 Duo processor, 2gig of Corsair XMS2 DDR2 RAM, and an nVidia GeForce 7900 GS 256m video card. It’s got a 160g samsung and a 120g maxtor IDE drive, one with XP Pro and one with OS X Leopard. I’m able to use VMWare Fusion to boot windows inside os x, just as if it were installed with bootcamp. I’m also able to dual boot using the Windows boot loader.  So far, I haven’t noticed anything weird about the leopard install. It seems to run fine, without any problems.

I used the kalaway 10.5.1 dvd, and skiped the vanilla kernel, loaded sse2 support, nvidia desktop drivers, no sound drivers, no network drivers, and mbr boot. I also partitioned the harddrive with mbr instead of guid. I did have to install 3rd party drivers for the audio to work, but it was pretty straight forward, and the drivers are avaliable from the insainely mac forums.

I use a Macbook Pro at work, and I’m glad to finally have a mac I can use, and can force my wife to use, at home.

Tags: hackintosh, kalaway, leopard, mac, os x

Posted: June 30th, 2008 under Computers, os x.
Comments: 2

I’m looking to write a subversion best pratices guide for work, so the developers can keep conflicts to a minium, and everything repository-wise keeps running smoothly.

I’m looking for things like, when to create branches, when to merge back into trunk, when to commit, etc…

Leave some suggestions in the comments, and I’ll try to roll them into a catch-all guide that maybe some other people can use.

Tags: repository, Subversion, svn

Posted: June 30th, 2008 under Subversion.
Comments: none

Using a story to drive your development tasks is a good idea, even when there is only 1 team member. Writing stories helps you stay focused on the requirements without getting side-tracked into something that isn’t working toward the end goal of your app. There’s always time for script.aculo.us later! Using RSpec stories also means you have tests to run against your code so you know that fixing something probably didn’t break something else.

First thing you want to do is get the RSpec on Rails plugin installed, and generate the RSpec code.

$ ./script/plugin install git://github.com/dchelimsky/rspec.git
$ ./script/plugin install git://github.com/dchelimsky/rspec-rails.git
$ ./script/generate rspec

Stories are broken down into 2.5 files:

• 1. The Story file - Where the plain text story resides
• 2. The Step file - Where the different steps in your story are defined.
• 2.5 The Story runner file - The ruby code that kicks everything off.

Read more »

Tags: bdd, internet, rails, rspec, ruby, stories, testing

Posted: June 27th, 2008 under Ruby on Rails.
Comments: none

 Playing around with the partitions on my mac yesterday, i accidently deleted the efi partition (dumb of me, i know), but I figured it was about time for a reload, so i just sucked it up and wiped the mac clean. 

Going through and installing all the stuff i needed for development, i ran into a problem installing the native mysql bindings for ruby.

Read more »

Tags: bindings, gem, installation, mysql, rails, ruby

Posted: June 20th, 2008 under Ruby on Rails.
Comments: none