Post, Mark K wrote:
Now, for the CentOS system, the same methodology will be used, except for the file system labels. Once the two disks have been copied, you'll need to change the file system labels on the new disks. Otherwise, when you try to boot either the old system or the new one, you'll get complaints about duplicate labels, and experience a whole lot of pain (trust me on that one). So, for each file system you have on your original disk, do: e2label /dev/dasda1 e2label /dev/dasdb1 Note the label names. Say they are "/" and "/usr" respectively. Then change them on the new file systems: e2label /dev/dasdc1 /new e2label /dev/dadsd1 /usrnew Once you mount /dev/dasdc1 and /dev/dasdd1 on /mnt and /mnt/usr, edit /mnt/etc/fstab, and change the entries: LABEL=/ LABEL=/usr To LABEL=/new LABEL/usrnew That should be the only difference between the two OSes.
You can, of course, change to not using labels:-) I imagine that you can use the same labels if you edit /etc/zipl.conf. Note that, if you do this, you need to edit it on both systems: you don't want the DASD for either on the other. Depending on how many systems you have to do, you might write a script that starts with clean DASD and ends with a fresh clone. I can imagine such a script being part of a DR plan. I rather like the idea of a small fixer system that you can boot and use to fix any other. It doesn't have to be very big and it doesn't matter whether you use Debian, SUSE or Centos; you can chroot into the system at some point. On peecees I generally use Knoppix for this, but it doesn't have to be so enormous. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/ do not reply off-list ---------------------------------------------------------------------- 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
