Why I Went Back To iOS 4.3.3…For Now

I’ve been an unofficial beta tester of iOS 5 for about two weeks now. There are a lot of interesting features that I think have the capability to make my life easier. First and foremost is the revamped notification system. Not being pulled out of my current thoughts by a modal dialog box is a great thing. Being able to deal with alerts on my schedule is very liberating. Also of great import to me is the integration with Twitter.
Allowing me to tag contacts with Twitter handles helps me keep my nerd friends straight, and the ability to snap pictures and upload them directly to Twitter is very helpful for those that takes tons of snapshots, like Stephen Foskett. There are even more features that have promise, like iMessage.

So why, on the eve of my trip to Cisco Live 2011, did I put my phone into DFU mode and go back to 4.3.3? Well, for all the greatness that I found in the beta, there were a couple of things that gave me pause. Enough pause that when I knew I was going to be at a conference where I would be relying heavily on my phone to be my lifeline to the rest of the world for a week, I had to go back to something a little more polished. My biggest complaint about the beta release of iOS 5 was the abysmal battery life. I wasn’t on beta release 1, which by all accounts had a battery life best measured in minutes. I jumped in during beta 2, where things were much improved, or so the story went. However, I found my battery life to be noticeably worse. I hesitated to use my phone to check my email or Twitter feed for fear it wouldn’t last through the day. If I actually made a call on it, I had to recharge it on the way home from work to be sure it would hold out. My trip to the OSDE tweetup was marred by less than 10% battery power, which made status updates unrealistically optimistic. I know that battery life is always a fine balance to maintain. New features require even more power, and the antiquated battery in my 3GS is quickly approaching the end of its useful life. However, if the next beta doesn’t address the battery life issue with a little more tweaking, it will be a hard choice to make.

Another irritation was the overall lagginess of my phone. Apps would take an extra second or two to launch than normal. Pulling up information inside Facebook or Safari seemed to freeze every time. My new fancy camera app crashed so much it was unusable. The phone just seemed to stall, like a computer with an old, slow processor or inadequate amount of RAM. Again, I know that most of this is due to the code train not being
optimized yet for release and the apps not being optimized for iOS 5. Usually, these are the last things to get fixed before release, so I’m optimistic that things will clear up. However, these are the same complaints that iPhone 3G users had about iOS 4 when it was released. It seems that maybe Apple’s support of 2-year old hardware is spotty in some cases.

Tom’s Take

Beta testing is always a crapshoot. You are agreeing to test something that may not be ready for prime time. I’ve been beta testing things since I got into computers and networking, so I’m never shocked by what I get into. However, in recent years, companies have been using the beta tag a lot differently. They either keep something that’s ready for release in beta forever, like GMail, or they push unfinished code out the door and make
their customers unwilling beta testers, which can best be summed up by the old maxim, “Don’t install a new version of Windows until the first service pack is released.” While I like many of the new features of iOS 5, the lack of polish in the battery life and lag departments were enough to make me reconsider my decision this time. I especially find that part funny, since I’ve never been so attached to a device to care about what revision
of code is running on it. I might give beta 3 a shot (if there is one), but for now I’m going back to something that isn’t going to make me tote around a 500-foot extension cord and curse my phone twice as much as I do already.

Fruit Company Console: My Review of the Cisco Console Companion for iPad/iPhone

One of the major advantages to owning an iPad, or in some cases an iPhone, is that you have a mobile computer at your fingertips that is quite easy to carry around the datacenter or networking closet.  I have an iPad myself, and I find it very useful for documentation purposes.  Whether it be taking notes about the configuration of a specific device or looking up the PDF of a particular feature from Cisco’s website, the iPad has many uses.  However, if I find myself in need of connecting to a device such as a switch or a router, my iPad/iPhone options are limited.  I can use a telnet or SSH client to remote into the system, but if I don’t know the management IP or the username/password combination I can be sunk.  Or worse yet, if the switch has never been properly configured for remote access it becomes a moot point.  If I want to be able to use my trusty Cisco rollover console cable to get into the switch the old fashioned way, I have to lug out my behemoth Lenovo W701 laptop and get it ready, which can be quite an endeavor depending on the amount of room I have to work with or the amount of time that I’m going to spend consoled in, since my laptop has about 1.5 hours of battery life under the best of circumstances.  Add in the difficulties that I’ve faced with USB-to-serial adapters under Windows 7 64-bit and you can see why I’m reluctant to use the console.  However, there is hope for the best of these two worlds.

A company called Redpark has started selling a rollover cable with a 30-pin iDevice connector.  Engadget had a story about it HERE.  Naturally, I decided that I just had to have one of these.  You know…for work and stuff.  Anyway, I jumped right over to the Redpark website.  Hello sticker shock.  This baby is going to set you back a cool $69.  Add in more if you want shipping and handling (whatever that is), so expect to shell out about $80 to get it to your neck of the woods, more if you need to have one tomorrow.  That’s not all, folks!  Even if you do manage to get your hands on one of these little jewels, you still need an app to access the console.  Now those of you that looked at this excellent blog post by Ruhann about console access on a jailbroken iPad are all set.  The rest of us poor saps that haven’t jailbroken our iPads yet are in a bit of a lurch.  Fear not, because the company also has an official app on the App Store called Get Console (or Cisco Console Companion) that will give you console access.  For a measly $9.99.  After all, you’ve already spent $80 already, what’s a few dollars more?

Once my console cable arrived in the mail, I was a little underwhelmed by the packaging:

Not much to look at.  The contents of the box were even worse.  The console cable lovingly encased in bubble wrap, and this instruction sheet:

Bravo for making it straightforward and easy to read.  Off to the App Store to download my new app.  Except…”Cisco Console Companion” isn’t the official title of the app.  It’s “Get Console”, along with a big disclaimer that it is in no way associated with Cisco.  I’m guessing they had to use an alternate title in the app store because of some wonky trademark issues that Uncle John wasn’t too pleased about.  At any rate, it was a fast download and then I was off and running.

For the purposes of this test, I’m consoling into a Cisco Catalyst 3560 8-port switch.  Once I fired up the program, it popped up with a one-time reminder that it was only for Cisco devices and that it would check each device to ensure that it was a genuine Cisco product.  My best guess is this is there to prevent people from trying to use it as an Ethernet cable or something, because most reports I’ve seen says that it works just fine with any kind of device that uses a rollover cable, like Juniper, or HP, or what have you.  I didn’t test this out during my first run, but I will be testing it down the road of some of those devices.  Note that since it is an RJ-45 rollover cable, it can’t be used on RS-232 or null modem devices.  Oh well, time to upgrade those old switches anyway.  The cable itself feels rather thin, almost like a fiber patch cable rather than a flat rollover cable or even a UTP cable.  It’s about 6 feet long, so you don’t have to be right next to the device you’re trying to console into, but don’t expect to be programming from across the room.  Here’s a picture of the cable on top of my test switch:

My first encounter with the Get Console program led me to this screen:

Fairly utilitarian, but that’s fine by me.  I’m not really a “bells and whistles” kind of guy.  The bottom section of the screen is dominated by the on-screen keyboard, but that’s to be expected.  Just above that is a collapsible keyboard bar that lists some very useful control keys.  First is the all-important TAB key, which I’ve found sorely lacking on some of the telnet clients I’ve used.  TAB saves me a ton of time.  Next is the CTRL key, which when tapped toggles on and allows you to use CTRL+ shortcuts for moving around the command line or sending a CTRL+C or CTRL+Z to end.  Next is the BRK key, which sends an immediate break signal to the console.  Useful for those times when you need to enter ROMMON on bootup.  Next is everyone’s favorite question mark key.  Having it here is really helpful so that I don’t have to waste a keystroke getting to the number/symbol keyboard on the iPad.  This is followed by the up and down error keys, which are used to cycle through your command history forward and backward.  Lastly is a Return key, which I didn’t really use, since the iPad keyboard has one built in.

The upper right corner of the app replicates many of the same keys as the collapsible keyboard, along with a paper clip icon.  When you tap this, it pulls out a drawer that contains the contents of the clipboard.  You can paste those contents directly onto the command line.  So if you find yourself typing the same commands in over and over, this is a handy shortcut (there are others we’ll get to in a second).  As a quick note, while you can type in this clipboard, if you don’t copy the contents before pasting it will simply paste what was in the box before.  So be sure to copy before you paste.

The upper left includes the Settings button, the session button, the keyboard show/hide button, a button to show/hide the collapsible keyboard with the TAB and CTRL keys, and a file drawer for storing config files.  The settings button is very feature rich. You can choose to have the program automatically connect when it launches or wait for you to connect manually.  There are also settings to change the baud rate and stop bits, which really helps when you are connecting to some non-standard gear.  You can have the system log all of your console sessions, which can be stored in the filing cabinet for later examination.  You can change the number of columns and rows, as well as the amount of scrollback in the window.  Be aware that adding too many columns will mean you need to scroll the screen left or right to see the output, as it looks like the main window is about 80 columns wide.  You can change the bell that dings when you do something you aren’t supposed to, as well as changing the color scheme to something other than white-on-black text.  The font size slider doesn’t correspond to actual point sizes, so you might need to play around with it to find a comfortable setting.

The session button allows you to disconnect a console session manually as well as offering one of the added benefits of this program.  By signing up at http://www.get-console.com, you can add an option under settings to connect to a remote console server at that website.  You can then tap the session button and obtain a 7-digit access code that allows someone to access your console session from the Get Console webpage.  This is fairly handy if you have a junior administrator on site and need to walk them through a configuration.  Or if that same junior admin is in a network that is down, you can use a 3G iPad to connect to their console session and do some troubleshooting.  I had to play around with the settings in order to test this feature.  It looks like the app connects to the remote console server when you choose to share the session, and the access code allows the user on the website to connect in like a type of reverse telnet connection.  I couldn’t get the app to connect using the North America servers, but the Europe and Asia servers worked just fine.  However, the latency on these connections was pitiful.  Redraw on my screen could be measured in seconds.  I tried entering some commands on the webpage, but careful typing was enough to overrun the keyboard buffer for the app.  And if you’re going to try and look at live debugs, you might as well forget about it.  By the time you could send a break or “un all”, you’d be swamped in messages.  Better to use the web app as a mirroring device for training or for simple troubleshooting.  You can also choose to encrypt the sessions if you want, which is a pretty good idea if you don’t want everyone on the Internet up in your business.

The filing cabinet is another interesting piece.  By uploading configs to the Get Console website, you can store them in your filing cabinet to copy onto the device locally.  That way, if you have a template for your switches, you don’t need to worry about copying and pasting it out of an e-mail, where it may get buggered up by some strange formatting issues.  You can also have those pesky junior admins share an account and copy the configs to the filing cabinet for them, so all they have to do is walk out and plug in to setup the switch with enough config for you to be able to telnet to it.  There is local shortcut storage as well, so you can keep some of your more clever commands on your own iPad safe from those that could use them to do harm.  You can also store console logs for later upload or email.

Out of the box, the font size was downright tiny.  I had to bump the slider up to about 3/4ths of the way just to read it comfortably, and I was holding the iPad less than a foot from my face.  The keyboard was quite responsive, and the scrolling of the information was smooth and easy to follow.  The app is setup to beep at you when you try to use a key that isn’t supported, such as a down arrow at the prompt when there are no more commands to replay.  This feature is nice because it gives some feedback so you know when you’re beating your head against a brick wall.

In case you’re curious, this app is universal for both iPad and iPhone/iPod Touch.  But other than just glancing at the console I’m not sure how useful it’s going to be.  There isn’t much screen real estate to start with, and all the extra pieces don’t give you much room to look at things.  Here’s a screen shot to give you and idea of what I’m talking about:

Tom’s Take

It all comes down to money.  Is there enough utility in this cable and app for you to justify spending $100 on it?  Do you often find yourself in a network room with only your iPad and a switch that won’t respond to any other method of input?  I wouldn’t dream of trying to do any kind of heavy duty debugging on this device.  I’d rather have my full laptop with multiple apps and notepad windows to drag around to interpret console spam.  As well, any kind of programming that would require lots of time at the keyboard would probably get uncomfortable after a while, unless you’re one of those people that happens to like typing on the iPad on-screen keyboard.  I suppose you could haul along a wireless keyboard, but at that point you’re dragging along an awful lot of devices for simple console access.

I could see this being a useful tool for training or for an emergency tool kit.  Throw an iPad and a cable in your kit and you have instant access to the console of a device from anywhere in the world.  You could send the less-skilled network admins out on site and a more senior person could stay in the office and do some simple troubleshooting or configuration in order to get to the equipment through SSH or telnet.  The web piece, in my mind, is just too unresponsive to spend a lot of time on.  Plus, if you are fast typist like I am, you’re going to get rather frustrated with the delay in command execution, if you don’t outright lock the system up with all the characters you’re throwing at it.

The app does what it says, there’s no denying that.  I find it very useful to have on my iPad and I’ll probably use it going forward for many of my walkthroughs and audits.  However, I think the $100 price tag is a little steep for something like this.  I hope that the price of the console cable will come down at some point, because $69 dollars for this is a bit of a stretch, even by Apple standards.  If there is enough demand, we may even see some other vendors get into the market and offer something like this.  If that happens, hopefully the Get Console people will support them as well.  I had hoped that maybe the software people could offer a gift card with the purchase of the cable, but I believe that they are two different companies so that’s probably out of the question.  Redpark could always throw in a $10 iTunes gift card if the want to soften the blow of needing the additional app to use the cable, but marketing isn’t my department.

All in all, I think I’m going to be able to find some use out of this app.  However, you really need to think twice about whether or not a C-note is worth giving up for this type of functionality.  If you want to learn more about these products, you can check out the console cable at http://redpark.myshopify.com/products/console-cable and you can check out the software program at http://www.get-console.com/

Blu-Ray Blues

I don’t know if it made the news or not, but apparently Apple refreshed the Macbook Pro line this week.  Not a groundbreaking update, mind you, but more along the lines of a processor refresh and move back to ATI/AMD discrete graphics over the existing NVIDIA chips.  There was also the unveiling of the new Thunderbolt port, based on Intel’s Light Peak technology.  This new port is designed to be a high-speed data access pathway for multiple devices.  For now, the Mac will use it for storage and DisplayPort.  Remember this, you’ll see it again later.

There was a long list of rumored hardware that might make it in to the new units, from SSD boot drives to liquid metal cases to reduce weight.  As with many far-out rumors, there was little fire behind the smoke and mirrors.  One thing that I didn’t see in the rumor mill which has been generating some discussion the past few days was the inclusion of a Blu-Ray drive in the Macbook.  People have asked for the high capacity drive to be an option on the Macbook for a couple of years now.  Some people want the option to pop in an HD movie and watch away on their laptop.  Others would love the opportunity to have a Blu-Ray burner and create their own content in Final Cut Pro to later burn to disc.  Still others want to use that burner to archive large amounts of data and keep their drives nice and clean.  The arguments say that it’s time for Apple to step into the now and include an HD optical option.  They cite the fact that Apple was key in the formation of the Blu-Ray spec.  While I can empathize with those looking for an internal Blu-Ray option for their shiny new Macbook, I seriously doubt that it’s ever going to happen.  Why?

1.  Blu-Ray competes with iTunes. For those of you that want to use your Macbook to watch movies in all their HD glory, your current option is to use iTunes to purchase or rent them.  And that’s just the way Apple likes it.  If Apple were to include a Blu-Ray option on the Macbook, it would cut into the sales of HD content on iTunes.  Given the option to pay for wireless access at the airport and spend my time downloading a movie through iTunes and hope it gets pulled down by the time my flight takes off, or simply throwing a couple of Blu-Ray discs in my bag before I leave on my trip, I’ll gladly take the second option.  It’s just easier for me keep my entertainment content on removable media that can easily be swapped and doesn’t need an external battery pack to operate.  Plus, I’m the kind of person that tends to keep lots of data on my drive, so the available space for downloading those large HD movie files might not be available.  However, Apple doesn’t make any money from my Blu-Ray purchases from Amazon.  I think for that reason they’ll stick to the lowly DVD drive for the foreseeable future.

2.  The future of the Macbook isn’t optical. When the Macbook Air was released in October, Tim Cook heralded it as “the Mac of the future”.  While many focused on the solid state drive (SSD) providing the on-board storage or the small form factor, others looked at the removal of the SuperDrive and remarked that Apple was making a bold statement.  Think about the last time you used a CD or DVD to load a program.  I have lots of old programs on CD/DVD, but most of the new software I load is installed from a downloaded program file.  Even the large ISO files I download are mounted as virtual CD drives and installed that way to expedite the setup process.  Now, with the Mac App Store, Apple is trying to introduce a sole-source repository for software like they have on the iPhone/iPad/iPod.  By providing an online software warehouse and then removing the SuperDrive on their “newest” laptop, Apple wants to see if people are really going to miss the drive.  Much like the gradual death of the floppy drive, the less people think about the hardware, the more likely they won’t miss it if a computer company “forgets” to include it on cutting edge models.  Then, it’s a simple matter to remove it across all their lines and move on to bigger and better things.  At this point, I think Apple sees optical drives as a legacy option on their laptop lines, so going to the length of adding a new technology like Blu-Ray would be taking a technological step back for them.  Better to put that R&D effort into newer things.

3.  Thunderbolt creates different options for storage.  Notice the first peripheral showcased alongside Thunderbolt was a storage array.  I don’t think this was coincidental when considering our current argument.  For those Blu-Ray fans that talk about using the drive to burn Final Cut-created movies or data backups, Apple seems to be steering you in the direction of using direct storage attached through their cool new port.  Having an expandable drive array attached to a high-speed port negates the need for a Blu-Ray unit for backups.  Add in the fact that the RAID array would be more reliable than a plastic disc and you can see the appeal of the new Thunderbolt technology.  For you aspiring directors, copying you new motion picture masterpiece to a LaCie Thunderbolt-enabled external drive would allow you to distribute it as simply as you could on a Blu-Ray disc without needing to worry about having a file size limitation of the optical media.  For what it’s worth, if you go out and price a Blu-Ray burner online you’ll find that you can get an external RAID array for almost the same price.  I’d recommend the fine products from Drobo (don’t forget to use the coupon code DRIHOLLING to save a little more off the top).

As you can see, I think Apple has some very compelling reasons for not including a Blu-Ray drive on their Macbooks.  Whether it be idea that optical discs are “old” technology or the desire to not include competition for their cash cow, Apple doesn’t seem compelled to change out their SuperDrive technology any time soon.  But if I were you, I wouldn’t worry about getting the Blu-Ray blues any time soon.  With the way things are going with app stores and Thunderbolt storage arrays, in a few years you’ll look back on the SuperDrive in your old Macbook with the same fondness you had for the 5 1/4″ drive on your old Apple II.

The Abomination!

Sometimes I get bored.  Everybody does.  But when I get bored, strange things start happening.  I get restless.  I get devious.  And, this week, I got bored enough to get creative.  As such, I created The Abomination:

Yes, that is OS X Snow Leopard running on an ASUS EeePC 1000HE.  Who needs stinkin Macs, right???

Actually, this was a fascinating exploration into the way that operating systems are built.  I’ve been a closet Linux fan for years.  I can still remember working with Red Hat 6 when I interned at IBM.  And my backup machines around the house have always had some flavor of Linux on them.  I’ve emerged Gentoo and built Slackware.  I’ve dropped in Fedora and Ubuntu.  I’ve even used Debian.  Once.  So I’ve gotten a lot of practice installing OSes on systems.

Now, Mac has always fascinated me to a certain degree.  As much as Linux people are evangelistic, Mac people are downright zealous.  Up until my iPhone, I’d never really had the time or inclination to deal with Apple hardware or software.  But my opinion has always been that Mac software is significantly less buggy due to the fact that Apple has historically been a great hardware company.  Windows, for what it is, can install on lots of different hardware.  Net time you are in Best Buy, look at ALL the hardware you can buy for a PC.  And realize that all of it has to work with several different versions of Windows.  Now look at the Mac section (if there is one).  Probably a few white boxes.  Accessories.  No video cards.  No RAID controllers.  Everything you need comes in your Mac.  So, the OS only has to be written to encompass a small number of devices.  Most of the problems with Windows stem from misbehaving drives.  As such, if you only have to write drivers for a smaller subset of hardware, it’s a lot easier to stabilize your OS.  It’s also a lot easier to write to it’s fullest specifications, such as cute graphics like your icons bouncing on a toolbar.  So, it goes without saying that OS X is stable and flashy.  But it really only installs on Apple hardware.  Or so I thought…

Enter the guys over at Insanely Mac.  Those guys have installed OS X on everything that they could, including a toaster.  And so I started researching the forums, initially intending on installing OS X on my backup Lenovo/IBM Thinkpad T60.  Lo and behold, I find out that most of the hardware in the T60 will work, but my particular wireless card is a no-go.  But, the netbook that’s been lying on my desk collecting dust for the last six months is fully supported.  The camera, the wireless card, everything!  So off I set to complete my evil scheme.

I procured an OS X install disc.  Legally, of course.  The I read THIS THREAD. REPEATEDLY. I borrowed one of the Mac Guy’s systems.  I didn’t really tell him what I was doing.  I first tried to use an 8 GB USB drive to perform an install, but I could never get the OS to install correctly.  So I formulated Plan B and just pulled the drive out of the netbook and did a complete install.  I blew away the partitions and created a single OS X partition.  And an hour later, I have a complete OS X install on my netbook drive.  After reading the thread again, I downloaded the software to make the installation bootable.  I copied over the KEXT files (which are basically drivers for OS X).  And after all of that was completed, I disconnected the drive and reconnected it to my netbook.  And I rebooted.

This was possibly the most nerve wracking part.  I knew the installation was good, as the drive booted on an iMac.  But would it work on the netbook?  As the gray Apple boot screen spun and spun, I sat transfixed.  I waited for a crash or a kernel panic.  I was no stranger to kernel panics, so I knew if I could get a diagnostic message I’d be good.  But, that was not to be.  A frozen gray screen stayed up for about five minutes before I rebooted.  I checked my BIOS settings to make sure the settings listed in the forum guide were disabled.  This time on the reboot, things came up a little faster.  It turns out that OS X was building some system files in the background and I just needed to have a little more patience.  But finally, I was greeted with a desktop!

The camera worked.  Bluetooth worked (but I couldn’t turn it off).  But no connectivity.  Wired Ethernet was not there.  No WLAN card detected.  I figured that the networking would be the hardest part to configure, but I’m not The Networking Nerd for nothing!  As it turns out, the Ethernet driver was linked in the post.  After I copied it over to the netbook and did the convoluted driver install procedure for OS X, wired Ethernet worked after a reboot.  As the system came back up, I checked the BIOS once again for issues and found that the dreaded “Boot Booster” was still enabled.  According to the Interwebs, Boot Booster caches BIOS settings from the last boot and uses them to speed boot times by about a second or two.  It also seems to freak out the WLAN card in OS X.  After I disabled the Boot Booster, the wireless card miraculously started working!

I updated the installation to 10.6.1 using a combo update and reapplied settings as outlined in the last page of the above thread.  I stopped there as Apple removed support for the Atom processor as of 10.6.2, requiring some nifty kernel patching to put the support back in.  I decided that 10.6.1 was acceptable enough for me right now for testing.  And so I’ve been using my little MacNetBook on and off for the last few days.  Based on the recoils of horror from some of my Twitter followers, I’ve even made the hostname ‘abomination’.

How do I like it?  So far, to me it doesn’t really feel much different than Linux.  There’s a bit of a learning curve (better than my Windows-to-Linux curve), and the software installation routine is much, much better than RPMs.  But all in all, I think I’m going to need to use it a little more to get a good opinion.  And I’m probably going to need to install it on a full-sized machine to use it more often than I do now.

In the end though, it was nice to prove that I could do something not entirely supported by anyone other than the community.  It brought back my Gentoo days, and all my original Linux fun from the Red Hat 6 days.  And it proved that no OS is locked down too tight given enough bored people out there.