Also don't forget to change your hostname. /etc/HOSTNAME in SLES8. If using Samba, also change it in /etc/smb.conf
and, just to be sure, re-run /sbin/SuSEconfig after you've made all the changes to the HOSTNAME and network files. LVM ought to come up automatically in SuSE if you've DDRed the volumes. If not, try vgchange -a If using ssh, I'd also do a rm /etc/ssh/*key* to force SuSE to rebuild all the ssh keys for the new system at its next boot so that you have different and unique ones. "An Optomist is just a pessimist with no job experience." - Scott Adams Gordon W. Wolfe, Ph.D. Boeing Enterprise Servers 425-865-5940 > ---------- > From: Taraka Srinivas Kumar > Reply To: Linux on 390 Port > Sent: Thursday, June 10, 2004 6:21 AM > To: [EMAIL PROTECTED] > Subject: Linux cloning - first time > > <<File: InterScan_Disclaimer.txt>> > > Greetings, > > We have SuSE linux on an LPAR at our installation. > I want to bring up another Linux LPAR. Thought the best way would be to clone the > existing linux. > > Is it OK, if i > 1.copy the existing volume(s) contents into a new set of volumes > 2.Mount these new volumes and change fdasd, zipl.conf, network files with the new > volume id's > 3.Bring up the new system > 4. Make corresponding changes so that LVM groups come up properly > > I am not sure how step 4 needs to be done. I have seen some discussion on vgchange > last week. Again please let me know your thoughts on achieving this. > > Please let me know the steps involved/ precautions to be taken in this exercise. > Also appreciate if pointers are provided to some documentation. > > Regards, > Srinivas. > > > ---------------------------------------------------------------------- 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
