>>> On 10/18/2012 at 09:43 AM, Ron Foster <[email protected]> wrote: > We are starting a journey from SLES10 SP4 to SLES11 SP2. Part of the journey > is building a a SLES11 enironment with certain capabilities. One of those > capabilities is the ability to boot the install CDs and then perform a > FDR/upstream restore from the environment provided by the install CDs. (I > know that we could boot another Linux system and reach out and do a restore, > but this procedure is for when that scenario will not work.) > > Anyway, our procedure calls for executing a devmap_mknod.sh script. It > appears that that script is not available in a SLES11 sp2 environment. It > also appears that /dev/ram3 is not available. > > Any ideas whether devmap_mknod.sh is necessary. Also about the ram3 > ramdisk.
I would have to say that devmap_mknod.sh is not necessary. That was from device-mapper 1.x, and it talks about devfs, the LVM1 control device and things like that. /dev/mapper/control doesn't even exist in LVM2. I suspect the reason you're not seeing things like /dev/ram3 is because on System z, even the rescue environment needs to be fetched from a network installation server, just like the installer does. Instead of the initrd integrating the installer code into the running system, it needs to integrate the rescue system code into the running system. I'm not sure that you can do what you want to do with the tools you're using. At least, not the way you seem to be trying to use them. Mark Post ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
