Lots of Updates before OS Mavericks

Apple made announcement on Noct 22, 2013 that the new Mac OS Mavericks released on the same date for free. What a surprise to all Mac users! That means all mac computer users as early as 2007 can get their Mac OS updated. I checked my 2008 MacBook Pro. It was not able to update to Mountain Lion, but now it is legitimate for update.

Here is the information about Mac OS Mavericks:

Last night I hold on the update. The reason one is to prepare for the update: checking all the updates available before updating.  Another reason is to wait for any issues related to Mavericks. So far, I have not notice any issues. As my schedule, I'll do my preparation updates first.

OS Update: Safari 6.1, iTunes 11.1.2...

Here is the space difference between before and after for the update:

Command: df -lak	Used(Kilobytes in 1024-blocks)
Before	…376,180
After	…402,852
Difference (A-B)	26,672
Capacity	48%

iBooks Author

Here is the space difference between before and after for the update:

Command: df -lak	Used(Kilobytes in 1024-blocks)
Before	…402,852
After	…584,468
Difference (A-B)	181,616
Capacity	48%

Apple Configurator

Here is the space difference between before and after for the update:

Command: df -lak	Used(Kilobytes in 1024-blocks)
Before	…68
After	…80
Difference (A-B)	12
Capacity	48%

Xcode 5.0.1

Here is the space difference between before and after for the update:

Command: df -lak	Used(Kilobytes in 1024-blocks)
Before	…584,480
After	…733,808
Difference (A-B)	149,328
Capacity	48%

By the way, I had trouble to use Safari after updating yesterday. My Safari kept crashing when it was opened. Fortunately, I has Chrome as a way to browse internet. I found that many people had similar issues, but different causes. Some are history to be cleaned, or Safari db files to be removed from Library folder. 

Eventually I found a solution for my case after I submitted my case. It was caused by Glims. I have to uninstall it or update it. I removed it from my Mac. After that, my Safari is stable.

One lesson learned from this incident: always be prepared for browser failure. Second one is valuable, even I don't use Google's Chrome in most of time.