On Tue, 22 Mar 2005 16:50:47 +0000, Alan Cox <[EMAIL PROTECTED]> wrote:
> On systems that matter a bit more I bring up another PC (I guess another > VM in 390 world), install on it and move /home straight over followed by > any 'user' data directories. > > After that you can generally just copy over the relevant configuration > from the /etc of the old machine. It is probably getting close to religion as how you approach that. I fully agree that this gives you full control over what is happening, but it does require the sysadmin to know where all application configuration is, and how the data is move from one server to the other. > For a live update back up /etc first and if you have the time do it a > release at a time not all in one. Also when you update at least for Red > Hat it is a good idea to upgrade rpm and the related tools as early as > possible as you can get in an interesting tangle if there are packages > wanting new rpm features. With Linux on z/VM it is easy to run the upgrade on a copy of your real disks, and see whether you like the result of it. And you could mount your old disks at a convenient place in the new system to copy over configuration things to the new system. Ideally you have the application data on separate disks and mount them back into your new system directly. But be careful not to create a mess by sneaking in code through the backdoor... I learned that with SLES you can even upgrade so that deprecated packages are replaced (otherwise you would keep those around forever). Because of the UnitedLinux sidetrip, there is no supported upgrade from SLES7 to SLES8 (other than re-install and copy the data). Rob -- Rob van der Heij rvdheij @ gmail.com ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
