Like Adam said: edit to the new dasd addresses /boot/parmfile /etc/zipl.conf
Run zipl Also - will you have the old and new DASD available in your LPAR for any amount of time during the cutover? It will make things easier to have the old DASD still visible to use as a rescue system in case things go awry. On 3/8/06, Kittendorf, Craig <[EMAIL PROTECTED]> wrote: > > Yes, the network devices remain the same. I fought that crisis a few > weeks ago. > > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Adam Thornton > Sent: Wednesday, March 08, 2006 8:01 PM > To: [email protected] > Subject: Re: New DASD > > On Mar 8, 2006, at 6:42 PM, Kittendorf, Craig wrote: > > > Once again: LPAR mode running SuSE Linux 7.2 (S390) - Kernel 2.4.7-SMP > > and moving to new dasd. > > > > What about changing the current dasd addresses in the following: > > /boot/parmfile > > /proc/dasd/devices > > /etc/zipl.conf > > to the new dasd addresses. > > > > Don't need to do /proc/dasd/devices; it's generated by the kernel. > > > Run zipl? > > Anything else? > > Will your network devices be at the same addresses? > > ---------------------------------------------------------------------- > 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 > -- Jay Brenneman ---------------------------------------------------------------------- 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
