On 1 May 2003, seth vidal wrote: > > > My general rule is if you're going to do an in-place system upgrade is > this: Test Test Test on machines where their continued functioning is > non-essential. > I like to test on beta hardware first, then look at what broke and do it again a few times until I feel comfortable with the gotchas. After which I like to closely look at what the system is running and has installed and purge all the crap that doesn't need to be there or can be easily reinstalled after upgrade (smaller deltas can't be bad, and a good exam of your system is always good), backup important things to some other machine and then run the upgrade, noting everything that gets spit out on stderr and then resolving those issues before rebooting. After reboot start tuning on and playing with things one at a time until I feel comfortable. If things go horribly wrong, I can always fresh install the older version and restore the backups and be runnign again quickly. I also try to keep machines as vanilla as possible. This isn't always doable so those are the machines that get a fresh install, as it's not worth the time to track down every issue. > You'd be shocked how often things get broken. > Nope. This is why I stopped using RedCarpet, every ximian package conflicted with everything else and frequently made a mess out of things. Ok.. I'm sorry.. I've taken this way OT now. I'll shut up. Again, thanks for the advice Seth! -n -- ---------------------------------------- nathan hruby <nathan@xxxxxxxxxxxxx> computer services specialist uga drama & theatre reality is a moving target ----------------------------------------
