Hi, Yes, but.... In my example, I was making the old and new root disks available to a second system. In a follow-on note to mine, Mark Post gave an example of doing it all on one system. I suggest that you look at his method first.
---------------------------- From Mark's Post Taking the system out of service for such a long period of time can easily be avoided by: 1. Adding the new disk to the existing system dynamically 2. Doing the same dasdmft, fdasd and mke2fs. 3. Following the HOWTO at http://linuxvm.org/Info/HOWTOs/movefs.html from steps 3 to 4, but doing the "cd" to /, instead of /usr. 4. chroot to /mnt 5. Update /etc/zipl.conf, but only if any device numbers will change. 6. Run zipl 7. exit the chroot environment 8. Unmount the new file system. 9. Reboot at the time of your choice. This also eliminates the need to modify all the other parameters in /etc/zipl.conf to remove the /mnt from the directory paths. Mark Post tom - - - - - - - - - - - - Linux on 390 Port <[email protected]> wrote on 12/29/2004 12:19:59 PM: > For us "non-VM" aware users, can I assume that the command "CP LINK" causes > the new root disk to be available -- aka "online", to the original or > (old/source) system? <...snip...> ---------------------------------------------------------------------- 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
