Ok, I got both iPhones upgraded to the 2.0 version of the iPhone OS.
Initially, I had some trepidation about upgrading a day early … and my feeling seemed to be valid when a co-worker tried to upgrade his phone and had a bunch of problems. He kept getting an “Unknown error (6)” message. I don’t know if he actually got his upgraded.
Regardless, I decided to throw caution to the wind and upgrade my phone anyways. Luckily, it worked without a single hitch.
When I got home from work, I proceeded to upgrade Ginny’s phone. This, of course, is where I ran into problems.
I started the upgrade process by first upgrading her iTunes to 7.7. That worked without any problems. Then I proceeded to upgrade her phone.
Initially it was going OK … then I got an “Unknown error (10)” message. Figuring that I would just restore the phone to it’s previous OS version, I tried the restore option … but when I did this I got an “Unknow error (20)” message. Tried a few more times and got the same message. This is not good.
I Googled around a bit and found a thread in the Apple support forum that said that, if I pressed Option (shift in Windows context) and clicked the restore button, I could ‘Recover’ to the 2.0 firmware. Luckily this worked.
About 20 minutes later I had Ginny’s iPhone working fine.
Five minutes after that, I we were both playing with the “Phone Saber” application.
Yep, it happened again … about this time last year I was trying to upgrade my servers to Fedora Core 6 and ran into some problems.
Well, I decided it was time to upgrade to Fedora 8 … and, since I have time off, I figured this was a fine time to do it again.
Of course, in retrospect … there never would have been a good time to do the upgrade, based on the problems I encountered. At least I know my backup procedure is fairly good now.
I had been planning this upgrade for weeks … everything was set. In fact, the first half of the upgrade went smooth as silk. I upgraded the main web server (gondor) to Fedora 8 and it went pretty nicely. Only two issues, both of which were solved after a little research.
This gave me the confidence to proceed to upgrade Rivendell to Fedora 8.
I started the upgrade by booting from the CD so I could install Fedora from the DVD ISO image I had on a USB hard drive. Problem is, the system wouldn’t boot this way.
There were a few minor glitches … but nothing that couldn’t be handled.
One thing that was kind of annoying is the fact that the Apache config (httpd.conf) was replaced on both servers (the original was backed up to a ‘rpmsave’ file). This, in itself, wasn’t that big a deal … but I wasn’t expecting it.
I have an idea for a good open source project … that could be incorporated into new distribution releases … an “Upgrade Impact Analysis” tool. It would evaluate your existing configuration, compare to what is known about a new distribution, and tell you what config files could be used without modification and which files would have to be reworked.
Another problem I had, which had me worried, was the fact that I couldn’t get ClamAV to rebuild. After a bit of research, I found that my linker configuration file ‘ld.so.conf’ had a ‘/usr/i486-linux-libc5/lib’ listed. This has to be left over from one of my older Redhat installs. The files in that directory are timestamped April 15th 1999. To be honest, I’m shocked I was able to build anything with that old code in the linkers configuration. Luckily, simply commenting that line out fixed the problem.
So far everything seems to be working OK, so I’m cautiously optimistic.