System information

38 Sharing and maintaining SLES 10 SP2 Linux under z/VM
The boot.findself script is set to run at boot time with the chkconfig command and verified
with chkconfig --list:
# chkconfig boot.findself on
# chkconfig --list boot.findself
boot.findself 0:off 1:off 2:off 3:off 4:off 5:off 6:off B:on
See “The boot.findself script” on page 67 for a listing of the code and a brief description of the
logic.
Creating empty mount points under /opt/
Mounting middleware binaries read-only is beyond the scope of this paper. However, if there
is a possibility that you may run WebSphere® Application Server, DB2 UDB, or MQ Series,
you may wish to create the following, or other, empty mount points for other software:
򐂰 /opt/IBM/WebSphere/
򐂰 /opt/mqm/
򐂰 /opt/IBM/db2/
In this fashion, all cloned servers will have empty mount points for possibly mounting
software.
# cd /opt
# mkdir mqm IBM
# cd IBM
# mkdir WebSphere db2
Other modifications
These are only a few modifications to the base system. You may choose many other
modifications such as adding more RPMs, removing unnecessary RPMS, setting the
software clock correctly via NTP, etc.
Testing your system
The next step is to perform all tests that are necessary and appropriate for your environment.
The last step
Now the cloneprep.sh script can be run. The output should be similar to the following:
# cloneprep.sh
rm: cannot remove `/var/log/*.gz': No such file or directory
System should be ready for shutdown and cloning
Shutdown the test system and log off the z/VM user ID.
# shutdown -h now
...
Logoff the S10RWTST user ID. The system should now be ready to clone.
1.5.7 Copying Linux from S10RWTST to S10RWMNT
Once the test system has been modified and thoroughly tested, it can be copied back to the
maintenance system via the TST2MNT EXEC from the CMSCLONE user ID:
==> tst2mnt
Checking that source and target user IDs are logged off
HCPCQU045E S10RWTST not logged on
HCPCQU045E S10RWMNT not logged on