Rick, can you elaborate a little on you avoid putting " WWPN+LUN addressing to the initial RAMDISK"? Is your home-grown script run by CMS pre-Linux-boot or run by Linux early during Linux boot?
-------------------------------------------------------- This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Richard Troth Sent: Friday, April 06, 2007 10:51 AM To: [email protected] Subject: Re: Pros/Cons of FCP connection DASD <snip> We do not want to wire-in the WWPN+LUN addressing to the initial RAMDISK, which is how the distributor would like to support SAN. Stamping CKD addresses into the INITRD for virtual machines is one thing. Stamping WW addressing which varies from guest to guest is quite another. As a result, we have a simple home-grown script that reads a per-guest config and brings the right volumes on-line. But this is minor. It works. <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
