I know you’re a sweet little Jailbreaker

All together now…

You know you’re a sweet little codemaker
Oh yeah
And I know you’re a sweet little jailbreaker
I know you are, baby!

I made up my mind
Tired of wasting all my precious time
You’ve got to be all mine, all mine
Oh, foxy lady!

(Jimi Hendrix – Foxy Lady)

This post is best read while listening to “Foxy Lady” By Hendrix…

OK, So I have had my nice new iPhone for a month now, so that’s long enough to keep it new and work out how to use it, so its now time to JailBreak the sucker and get some Linux functionality on there.

So. I’m armerd with the following :-

iphone

  1. An Apple 3G 16Gig iPhone
  2. A usb link cable
  3. QuickPwn
  4. Some Cans of Beer
  5. A low boredom threshold.

So Lets begin.

Step 1: Open can, and pour drink into a pint glass (I’m civilized you know). Plug iphone into computer and back it all up using itunes.

Step 2: Run QuickPwn, and follow the helpfull instructions, Open Can and drink beer (OK, we doing techy stuff now, ignore niceties like glasses it gets in the way)

Step 3: Reboot iPhone with all your fingers crossed, Grab another Drink while waiting……… “Please Come Back UP!

Step 4: Unplug JailBroken iphone, and start adding sshd, Linux commands, and useful applications.

Step 5: Finish off the beers while watching NCIS… Why Do I never meet Geeks like Abby!!!

CN

Blog V3

Well that was the shortest lived Blog ever in the history of the blogosphere!

Allow me to explain. Are you sitting comfortably? Then I shall begin!

The blog V2 was up and running, GothNinja had imported his old Livejournal entries, and everything was all speed ahead, And *Crash!* did nobody spot the iceberg?

Basically my “new and improved” hosting providers had technical glitches, and three times in as many days all work was lost as they went to backups. And all new posts were lost, This was on top of random outtages in accesing the server.

So after some research a New New and Improved server was procured and the blog was given a new lease of life. Hopefully this time we will be staying put.

CN

IT workers + Coffee = Peace

There should be a form of Caffeine-Breathalyser fitted to all computers that prevent incoming emails unless the operator has a sufficient amount of caffeine in their system to cope with lUsers.

For my example I shall use my morning.

9am: Get into office, log into everything, say good morning to fellow staff, people on the internet, go grab coffee. (1st work coffee off day)

9:45: Check emails (Caffeine levels too low) Receive email from “FFS” Email basically states with lots of SHOUTY emphasis that I have not set up a live & development server correctly, and have set both to be same machine, with no access to development one, The email then goes on to list the server specs at me.

Now. This is where the caffeine lockout should have been enforced. Unfortunatly, due to this IMPORTANT piece of IT hardware not being yet invented, there was nothing preventing me replying to the email, and CC’ing the MD of FFS in as well for good measure. Basically pointing out the ineptatude of the developer emailing me, and the fact he has no clue as to what he is doing, did not bother checking, or doing anything before disturbing me. It was a work of pre-caffeine level Rant-Art.

10:16: MD of FFS emails a groveling appology.

Please, will someone invent the Caffeinalizer cutout?

Busby Pt. 4

It gets better…
After a week trying to evaluate My last “Data FileBusby have decided they are unable to evaluate the data due to their system still being broke from my last test. So to speed things up they are simply granting me access to their Live system as of Friday.

Oh the power… A new system to find the bugs in…

Busby Pt. 3

An update on the progress of my project with “Busby” is about due.

As you are aware from my previous posts, this project is all about integrating with some old archaic parts of the Internet. For those of you interested in how old, I spotted a variable $Noah.

Well we recently hit a problem where every test we put through broke their system in such a way that they could not reproduce the error even using the test data we provided. Got to love old code.

Well their engineers worked night and day for the last week and have finally fixed the problem.  They rolled back the code to a moth ago before they made any changes.  I believe the old Internet code has become self aware, and is resistant to change.

SkyNet is coming.