lssmit02 said:
From what I can tell, if you are happy with how Panther is running (from a stability point of view, not a features point of view 🙂 ), just upgrade to Tiger. Is there really a chance that any part of the system won't be replaced by the upgrade path? If so, what is it, and does it matter?
For the most part you are right, and most people won't see a problem.
The part that upgrade doesn't necessarily touch is the system configuration like /etc /var and the like. It tries to be smart and retain the settings and changes that were made on the older system, and this can run you into problems if there is a newer version of the software that doesn't work well with these settings, or you've installed extra software that conflicts (for instance you're running a custom version of qmail, and tiger is installing and starting postfix). Other things like jobs that used to be in crontab, but now are in Tiger's new deamon start system could be problems.
If this happens, the problem won't be obvious and will likely show itself in wierd and unintuituve ways that you will probably just write off as Tiger's instability.
The more customizations you do to your system, the more likely something like this is to show up. OTOH if you don't touch the system files, don't install hacks and plugins, you're probably safe just to do an upgrade. That's why there is so much dissent between the upgrade and archive/install camps. Neither has ever had the other's experience, because they use their systems so differently.
Doesn't an archive and install of Tiger where you preserve all your settings and import the home directory just reinstall all of the "problems" that would be present in an upgrade of Tiger? If this is wrong, I'd love to understand why, because then I would do the archive and install option.
Not necessarily, because the archive and install only preserves the settings under your user directory which shouldn't be affected by software upgrades. If they are it's fairly easy to trash the plist, because it will show up in an individual application, instead of something that's buried deeper in the system.
The reason to do an archive and install is that a conflict, if it does arise, will likely be very difficult to identify and correct. You may not even realize it's a problem and just be disappointed in Tiger. So for the most part, even though most people probably won't run into a problem, it's safer to do the archive and install and not have to worry about it.
It also helps clean out the crud that tends to accumulate in the system directories.