Update me softly
Back in the days when I used to write on the Apple Discussions Forums under the pseudonym of Mimi — I know, I know —, the Mac OS X Installer was a rather sorry mess. Today, it's a fine piece of updating goodness, save for one particular weakness: it does not automatically download and install updates on a freshly initialized Mac.
Those of us who held Mac OS X's hand as it was taking its first steps into this big, bright world remember the many horror stories that used to accompany every major release: hosed computers, screens blue, black or gray and long beeps were, at the time, common ills. Luckily, none of it was grave, and a re-install — with no loss of data — was usually all one needed to do to solve it all in one fell swoop. Little, however, did most users know.
Strangely enough, it took Apple four years or so to realize none of these issues were Mac OS X's fault per se but instead stemmed from many small and cumulative faux-pas in the installation experience. By adding simple tweaks to the process, without even changing the overall experience, they have solved most of these once-common issues.
We now have automated DVD verification, we have a migration assistant and, most importantly, we have plenty of little safeguards here and there that check for potential issues before updating the system. Sure, I wish more emphasis were placed on Erase and Installs instead of updates, but that's my old-fashioned streak.
My biggest regret is that the Mac OS X installer now does networking, meaning any Mac booted from the install CD becomes a potentially vulnerable networked machine, missing out on weeks, if not months of security patches. I guess, however, that normal folks do not worry about such issues, and that the actual window for infection is minimal.
Compared to the end-user experience when installing Windows XP or Vista or even Linux, both of which I have installed both recently and many times over the years, the Mac OS X installer is in a class of its own. There's no weird text to see running across the screen, there are no unexplained waits, no return to deprecated color schemes or screen resolutions. It's a full Mac OS X experience from the get-go.
Yet, Ubuntu and other Linux distros have one thing over the Mac OS X installer: if they find a network connection — and they're no better at it than Mac OS X —, they download and install updates as part of the initial process. This means that as soon as you bring your machine up, it's up-to-date and ready to go or to receive the latest third-party software.
Sure, Mac OS X will rely on Software Update to do this job after the installation, and a fresh Mac won't stay un-patched for long. Nevertheless, that is one extra step, that users can too easily delay or dismiss, creating a window for trouble by allowing users to install third-party applications on an outdated system — or connect external hard drives or enable FileVault or mount network shares
Downloading packages over a network without warning the user is a big no-no. One could, nevertheless, imagine an extra screen at the end of the installation process, before the offer to reboot is displayed, that would suggest the user pre-update the installation.
For all my love of auto-updates, however, I would never advocate doing things the Linux way and making the downloads mandatory. Indeed, knowing one can install a full, working OS without access to the Internet is a comforting thought.
Categories
MacRead More Entries by FJ de Kermadec.

thank you for this post.
Hi FJ
Three arguments against updates being applied inline with a system reinstall as you describe...
1) a (very) slow internet connection. At a rough estimate, you're currently looking at over 600MB for the various core updaters for Leopard alone.
The big ones I noticed were the 10.5.5 delta update - 316MB, the last security update - 31MB, the recent Java update - 137MB, iTunes - 56MB and Quicktime - 65MB. And that's disregarding all the other smaller updates - and machine specific updates too.
And then there's the individual iLife updaters if you've your machine is less than a year(?) old. iPhoto - 74MB, iMovie - 38MB, iWeb - 35MB. That's another 147MB.
That would take me all night (and I mean from going to bed through to getting up in the morning - not simply all evening) to download on my crappy old broadband connection - if I was lucky. What I do is download the standalone installers separately (usually at work where we have a very fat pipe) and have them on standby to install manually.
2) Say a user was having a problem due to a conflict from the latest OS update - say 10.5.6 - which forced them to reinstall. Your "concern" would have them updated straight back to the problem they had before. Whereas, the way it is just now a user can download the previous updater, say 10.5.5, and (hopefully) get back to where they were.
3) Take a business environment where the IT department has standardised/frozen a configuration at a certain point in time. Again, they'd need to be able to get back to that specific position if a machine was reinstalled. (Yes, I know that this last example is a bit fuzzier - they /should/ have images from which to reinstall, etc. But you do get my general point, yes?)
Please - leave us with at least the clear option to defer updates until after the reboot. :-)
Regards,
Gary the IT Guy