So, I’ve been drooling over finally having a nice laptop, which will allow me to do some CUDA development without tying me to my desk. I went out and got the new MacBook (you know solid aluminium…etc). Totally filled with excitement I immediately download the CUDA toolkit and SDK to see just what it can do.

Well, as it turns out not much. I was actually seeing a psychotic flickering while running the nbody simulation. Turns out there is a quick fix, which boggles the mind as to why it wasn’t on by default. Thus I share with you. During the installation of the CUDA toolkit, you must select “Customize” during the install and select to install the CUDA kext. After which you should be ready to run some major amounts of data.

What remains so odd about this is that the kext should have been installed by default, even the description of this install option it says something like “allows you to use CUDA”.. I mean WTF so I’d be installing the toolkit and not wanting to use it?

25-30 Gflops later..I am a very, very happy camper.

In the wee hours of the morning as I work on compiling random bits and pieces here and there I stumbled across a problem when attempting to compile gd and have it recognize my jpeg-6b libraries. I thought it worth noting that gd is specifically looking for ‘libjpeg.so’, which on my particular system doesn’t exist, instead I have a copy of ‘libjpeg.so.62′ which I simply created a softlink to the file and ran ‘configure’ again.

Don’t forget to set your CPPFLAGS environment variable to include your jpeg-6b header files!!

Once again all is right with the world.

Well now that I have all the tag-lines out of the way. I figured I would just share my simple help for installing the new Firefox 2.0 (released today) for Ubuntu … well you already know the rest.

To begin at the beginning. You need to create your .mozconfig file. Your best bet is just put this in your home directory. You can scrutinize the following, or just accept it as is, but this is my .mozconfig file.

The next item of business is of course to go download a copy of the new Firefox source (yes it’s early enough that we are going to have to compile it, if you haven’t already guessed that).

I don’t want to direct anyone to any particular FTP as apparently there has been some concern about this lately about bandwidth. Simply find a copy for yourself and extract it into your favorite build directory.

You are only going to need to write two more commands after you’ve finished extracting the files (from inside the mozilla directory in your extraction folder).

Enjoy!

At work lately I’ve been developing a SOAP interface from a third party vendor we are currently using. In the process I’ve decided to use Ruby to do this. I need to learn more Ruby and I thought it would be easier to use than the last time I worked with Python and SOAP.

Thus far everything is working great, the only annoyance I have is that I keep getting this as output from my connection:

Some quick Googling turnes up this command:

I included the first two lines to give context on how this was used and how it doesn’t precisely carry over to the SOAP module becuase it isn’t an option inherited by the SOAP object.

However I figured that the SOAP module must be creating an HTTP connection in there somewhere. So I decided to quickly jump into the source code and see what I can find. I located a single line in the source code for creating the HTTP object similar to how it’s used above.

After quickly firing up my vi and adding the line:

Even though it isn’t specifically creating a HTTPS connection here it ended up silencing the warnings. So I’ll just leave my code this way and enjoy it being much, much quieter.