System information

Sharing and maintaining SLES 10 SP2 Linux under z/VM 33
vm/CLONERO.EXEC
vm/CLONERW.EXEC
vm/MNT2GOLD.EXEC
vm/MNT2TST.EXEC
vm/PROFILE.EXEC
vm/RO2GOLD.EXEC
vm/TST2MNT.EXEC
vm/COPYMDSK.EXEC
vm/SAMPLE.PARM-S10
vm/SLES10S2.EXEC
vm/LINKED.EXEC
vm/PROFILE.XEDIT
vm/RO2GOLD2.EXEC
vm/SWAPGEN.EXEC
You should see a README file and directories vm/ whose files should have already been copied
to z/VM, and sbin/ for Linux files:
# ls sbin
boot.findself cloneprep.sh fstab.ror mnt2rogld.sh
boot.rootfsck.diffs fstab.dcss mnt2rogld-dcss.sh offliner.sh
These files will be used in the construction of the read-only root system.
Setting the cmm and vmcp module to be loaded
When the cmm module is loaded, in conjunction with configuration changes on z/VM,
significant performance gains are possible. Collaborative Memory Management and VMRM
are discussed in more detail in 1.9.3, “Enabling Collaborative Memory Management (CMM)”
on page 66.
The vmcp module allows CP commands to be issued from Linux.
The cmm and vmcp modules are added to the file /etc/sysconfig/kernel. This will cause
these modules to be loaded at boot time:
# cd /etc/sysconfig
# vi kernel // modify one line
MODULES_LOADED_ON_BOOT="cmm vmcp"
The Linux system running on the LNXCLONE user ID should now be configured.
1.5.5 Copying Linux from S10RWMNT to S10RWTST
You should now be ready to start the mechanics of creating a read-write maintenance
system.
Shutdown the golden Linux running on S10RWMNT is shut down and the user ID is logged off so
the system can be copied.
# shutdown -h now
Broadcast message from root (pts/0) (Thu Jun 25 10:35:59 2009):
The system is going down for system halt NOW!
... (and LOGOFF from a 3270 session on S10RWTST)
The minidisks 1B0 to 1B8 are copied from the newly installed S10RWMNT to the corresponding
minidisks on S10RWTST. Linux is IPLed on S10RWTST. Then modifications are made to the Linux