John asked: > 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?
Runs in Linux. It is not a CMS program, but reads one or more CMS files. For SuSE, it runs in the "boot.d" section: boot.ldfcpmap start for "load FCP map". It reads a CMS file which is maintained by our provisioning logic. The FCP adapters must be attached to the guest. Since we don't give Linux guests any VM privs beyond Class G, this is done for them. (There is no logic in 'ldfcpmap' for FCP attachment.) Right now, we're pursuing two paths for every LUN, and this script is capable of binding multiple paths to the same logical device in Linux space: $ cat /proc/partitions ... 8 0 35354880 sda 8 16 35354880 sdb 253 0 35354880 dm-0 ... Here, /dev/sda and /dev/sdb are the physical paths to the one LUN. Dev mapper binds them as /dev/dm-0. (There is a consistent logical name, which dev mapper also handles. But that name does not show up under /proc/partitions.) I then ran 'mke2fs -j' on the bound device and mounted it. -- R; ---------------------------------------------------------------------- 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
