ezmkverify & ezverify
Ezbackup, ezcustom, ezinstall, and ezmkverify/ezverify are used when building distribution media (boot diskette, installation diskette and backup media) perform routine system and/or user data backups and produce new distribution media when a system configuration change is made. Ezfilter and ezupdate are used to update existing AIX configurations.
The EZ-UTILITIES package is designed to aid
in the propagation of a master system to a target machine. The use of these
utilities assumes that the master system is fully installed and configured,
then cloned or minimally tailored. The purpose of the EZ-UTILITIES is to
During the actual installation phase of the EZ utilities, a disk space check is done on the target machine. If the target machine is smaller than the master system, an error message is provided and EZ install is aborted. Check the fsmap1 file described below for the actual disk space needed on the target machine to perform the installation. If the targer machine is larger than or equal to the master machine, the installation continues. A warning message is provided before any AIX minidisks is deleted. At this point, a user may choose 'n' to abort EZ install or choose 'y' to delete the minidisks and continue with the installation.
Note: If you choose 'n' to abort EZ install, you must remember to use the original boot diskette (NOT EZ boot) to reboot the system and restore the values which have been changed in NVRAM by EZ install. ezcustom must be run as super user.
Once the ezcustom script is started, the primary menu is displayed:
Chose the option by entering the corresponding number or "q". This menu returns after each option has completed.
The following are the options available from the ezcustom primary menu:
 Make boot diskette This option creates a single diskette or multiple diskettes which are used when booting the new system.
Informational messages will first be displayed.
Then the system inquires if you wish to format
Then the following message is displayed:
Insert the diskette to create the boot diskette. The primary menu is re-displayed when finished.
 Make install diskette This option creates a customized install diskette based upon the current system's configurations. The current system's install diskette and a blank diskette are required for execution of this option.
First a message stating that the contents of the /etc/install_devs file is being read is displayed. Then a menu listing the entries contained in this file is displayed. This menu is used to determine which devices will be eligible installation devices. To choose those devices to be installed on the system, enter the number corresponding to the name of the desired device. A comma or space should be placed between each number. Press the enter key to choose all the devices listed. If no specific devices are chosen the maximum number will be selected (from the top to the bottom of the list).
The selected device entries (as taken from the /etc/install_devs file) are put into a file called inst_devs, and placed in the /etc directory on the new install diskette.
When the following prompt appears, insert the write-protected master install diskette when the following prompt appears:
Please insert the write-protected
MASTER INSTALL DISKETTE to be
NOTE: This diskette must be write-protected.
Next the following prompt for the blank diskette is displayed:
Please replace THE MASTER INSTALL
DISKETTE in /dev/fd0 with a
You will be asked if this diskette requires formatting. This diskette must be write enabled, as it will be used to create the customized install diskette.
Next the following query is displayed:
Delete all user minidisks when using this INSTALL DISK?(default: yes)
This query provides information for installation on the target system. Enter 'no' to keep user minidisks, or 'yes' to have user minidisks deleted in the new system.
Once writing to the install diskette is complete, the primary menu is re-displayed.
 Change defaults
This option allows for modification of the default values used by ezcustom.
The change defaults menu screen appears as:
Descriptions of these fields are as follows:
Once execution of ezcustom has completed, the diskettes produced should be copied, and the originals stored in a safe place.
During execution of ezcustom, two files are created. These files are used during the installation process. The files created are /etc/fsmap1 and /nvram1. Both files are in ASCII text format and may be edited after the customized diskette containing the file is mounted.
The /etc/fsmap1 file is placed on the customized install diskette. This file contains descriptions of the AIX minidisks present on the master system. This file is used during target system installation to create minidisks which are copies of the master system.
If the first line is "yes", all minidisks are deleted. If the first line is "no", system minidisks are deleted, but user minidisks are not. The default is "no".
The following lines contain four fields separated
by white space. These fields are:
Comments are not allowed. Minidisks that are not being created must have a zero value as the minidisk size.
An example of the fsmap1 file:
The previous example deletes all minidisks, does not create the /u minidisk, creates / on hdisk0 with a size of 45000 blks and 4500 inodes, creates the local minidisk, /aixps, on hdisk1 with a size of 12000 blocks and 1200 inodes, creates the /tmp minidisk on /aixps/tmp on hdisk0 with a size of 9000 and 100 inodes, and creates a user minidisk on hdisk1 with a size of 4000 blocks and 400 inodes
The /nvram1 file is placed on the customized boot diskette. It contains descriptions of the contents of the master system's NVRAM. During target system installations, this file is referenced to update the target system's NVRAM.
The /nvram1 file contains the following information:
The keyboard language to use
This data is structured in the manner shown above, with one entry per line. A sample nvram1 file would appear as:
This machine's NVRAM would be set up with US English as the keyboard language, the display type as 8503, the time zone as Central Standard Time, Daylight saving time as being observed, the NLS translation language as US and the machine name as being aixtest.
1. If the input media has not been inserted
in the proper device, a prompt for the input media will be displayed.
Insert the input media into the proper device.
Enter elements (<cr> for all elements):
is shown, enter the names
of those FSUs to be put on the customized update media, and press Enter.
These names should be separated by white space.
ezfilter may be run multiple times to consolidate various FSUs from an update media set. It must be run at least once for every update media set that contributes FSUs to the update image used by ezupdate. Each time ezfilter is run the FSUs selected are added to those already present in the storage directory. FSUs can not be deleted from this directory. If a FSU is erroneously chosen, the storage directory must be deleted and ezfilter must be re-executed.
Should an FSU be selected multiple times, it will only be copied to the storage directory one time. Once a selected FSU is in the storage directory, it will not be overwritten. Subsequent selections of this FSU will be ignored.
The media produced by ezfilter is intended to be used with ezupdate for updating target machines and is also compatible with updatep.
-d input_device expects an argument specifying device from which update material will be taken.
-s storage_directory expects an argument specifying a directory where the FSUs being specified directory, ezfilter will display a warning message.
-o output_device expects an argument specifying the desired output device. '+' is used to specify no output. '-' is used to send the output to stdout.
An optional list of FSUs to include on the customized update media may be specified at the end of the command line. If this list is not included, a menu showing the possible FSUs to choose will be displayed during execution.
This command uses the /dev/fd0 device for input, stores the FSUs being extracted in the /local/updates directory, and outputs the contents of the /local/updates directory to the /dev/st0 device (Internal Tape Backup Unit). Specification of the FSUs being extracted occurs during ezfilter execution, when the FSU listing menu is displayed.
Ezverify is a program that runs after installation of a target system is complete. The ezverify program uses the verify.install file produced by ezmkverify as input to ensure that the files installed on the new system are the same as those found on the original master system. Ezverify can be made to execute automatically upon completion of installation by editing the /.post.custom file (uncomment the line invoking ezverify). The /.post.custom file is a script that is invoked at the conclusion of system installation.
Note: Ezmkverify must be run immediately prior to ezbackup to ensure that the verify.install file is present when ezbackup is run, and that the verify.install file accurately reflects the data present on the back up media. Executing ezverify after /.post.custom is invoked may produce invalid error messages.
1. Informational messages showing the progress of
ezupdate are displayed.
Messages beginning with "ezupdate:" are always output to the terminal where ezupdate was invoked. Messages beginning with a reference number (such as 048-088) go to stdout and may be redirected.
Also, if ezupdate fails and exits with an error, the integrity of the system cannot be ensured. It is best to use ezbackup to save the state of the system prior to running ezupdate.
Remote eupdate of a target system.
-F causes prerequisite check failures to be ignored and the update to be applied. All prerequisite failures are still reported.
-l logfile causes all output to be written to <logfile> rather than being sent to stdout. A message is displayed on screen stating output is being directed to <logfile>. This flag is ignored if the PTF image is to be read from diskettes (this requires volume exchange prompting). Use of this option allows ezupdate to run in the background.
-r results in an automatic shutdown and reboot following completion of the updates if the kernel has been rebuilt. This flag is ignored if the PTF media is on diskette because a reboot would not succeed with a PTF diskette mounted in the diskette drive. Default action is for manual reboot.
-s shows what steps would occur, but does not actually execute the updates. It lists which FSUs would have been updated. System checks are performed to make sure the system is ready for updating.
To update a machine from tape and then automatically reboot (if necessary):
This command invokes ezupdate using the /dev/st0
device (the Internal Tape Backup Unit) for input, automatically reboots
the machine after completion of the updates if a kernel rebuild occurs,
and directs output to /tmp/update.log.