Some time back I had to something like this. I was brand new to Linux and used the cp -R. Seemed to go ok but the numbers didn't match up when I finished. After talking with someone else he suggested I redo it using tar. The tar solution worked a lot better. Seems there are certain types of links that don't get handled correctly.
Definitely go the tar route. Bob Bates Enterprise Hosting Services - z/VM and z/Linux w. (972) 753-5967 c. (214) 907-5071 “This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rick Troth Sent: Tuesday, July 24, 2007 8:26 AM To: [email protected] Subject: Re: zLinux instance on Mod3 and need to move to a Mod 9 On Mon, 23 Jul 2007, Paul Raulerson wrote: > Well, yeah, but that won’t make the DASD bootable. > You need to copy over the boot sector as well, > > dd if=/dev/dasda1 of=/dev/dasdb1 bs=512 count=1 I believe the current DASD driver will get it right: dd if=/dev/dasda of=/dev/dasdb where if you copy the whole disk you'll get a working bootstrap. But this requires that the disk was formatted with 'dasdfmt' ahead of time. More accurately, it requires that the target was formatted with the same layout as the source. Adam's point is important. ZIPL is not only "traditional" but is the only way to be sure you have a bootstrap on the target disk that has been put in the right place (from what ZIPL can determine). The CDL layout in particular does "funny things" (my term) with track 0. -- R;
