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