Alan wrote: > rollback plan. Apache, php, modules, mod_perl, etc. No biggie at all > if it's your home server, but that's potentially a lot of downtime (ie: > a couple of hours) as I compile, test, re-jig the config files, test > more, etc. I'm in the same boat with postfix, running a 2.0.x when 2.2 >
if you're able, I'd look at linux-vserver or something similar where you can run a virtual machine (possibly using the same kernel), but in a different directory. Then you can copy a few websites/databases, perform the upgrades, fix what you need, document it (automate it), and then you can perform the REAL update. I had to do the same thing with the mysql upgrade from 3.x to 4.x. My apache upgrade, I just had to redo the configs by hand. php4 to php5 might be a bit more tricky. Currently that's the reason I have php5 masked... -- [EMAIL PROTECTED] mailing list
