This morning I got the motivation to attempt to make my blog format correctly on the iPhone. I expected it to be a lot more challenging then it really was. I began this project by reading the Apple provided Safari Web Content Guide for iPhone, specifically looking at Chapter 2: Configuring the Viewport. The viewport is how you tell your content, what the viewable area of the iPhone actually is.

Apple recommends that you set the viewport width to device-width so that the scale is 1.0 in portrait orientation and the viewport is not resized when the user changes to landscape orientation.

In part 1 of ‘jailbreaking the iPhone for UNIX geeks’: I touched on the jailbreak process and then covered installing the BSD Subsystem, SUID Lib Fix for the 1.1.3 firmware and fixing a small problem with the google maps ‘locate me’ application. I hope you enjoyed reading it, and now let’s jump right into part 2, and show off what the the jailbroken iPhone can really do.

For all of us UNIX geeks who purchased and love their iPhones, undoubtedly you have read about or heard about ‘jailbreaking’. At first it was a very complicated and possibly dangerous procedure to undertake, making it’s value questionable at best. But over time the jailbreak process for a 1.1.3 firmware iPhone, has finally matured to a ‘1-click-solution’. It’s reached a point where it’s easily done and also easily undone, so I decided to take the plunge and jailbreak my iPhone.

Sadly, I must preface the content of this post with the following statement:

I AM IN NO WAY RESPONSIBLE FOR YOUR IPHONE. JAILBREAKING WILL VIOLATE WARRANTIES AND SUCH, IF YOU CHOSE TO DO IT, YOU DO IT AT YOUR OWN RISK.

I am not going to go in depth into the actual jailbreak process, as I said earlier it’s a ‘1-click-solution’. I used the application called ZiPhone, available in both Windows and OSX versions, are available for download here. The method that I used, as I am a legitamite AT&T subscriber, was ‘Jailbreak’ only; if you are like me, there is no need to Active, or Unlock your iPhone. READ the included documentation, it’s straight forward and simple, however if anything goes wrong, see my disclaimer and their troubleshooting section.