HP Tru64 UNIX Technical Updates for the Version 5.1B and Higher Operating System and Patches (February 2010)

Correction to Configuration Cloning Restrictions (Nov. 2002)

In Section 7.4 of the Installation Guide — Advanced Topics, the second bullet explains that software

patches are not cloned. There are typographical errors in the procedure to use if your model

system has already been patched; the -f option is incorrect and should be -force. The following

is the corrected text:

• Software patches are not cloned. The reason for this restriction is that installed patches

change serial numbers, which will cause validation errors when the config.cdf file is

applied to the target system. The config.cdf file you create must be created from a model

system that has not been patched.

If the model system has already been patched, there are two alternatives you can follow,

although they are not recommended:

— Create the config.cdf from the patched system anyway. Use the -force option when

applying the config.cdf file to the target system to force the config.cdf onto the

target system. For example, at the target system, enter:

# sysman -clone -apply -force config.cdf

Then, at the newly cloned target system, create another config.cdf to use for cloning

additional systems. The new config.cdf will contain the correct checksums, and

cloning other systems from this file will be valid.

Caution:

The -force option to force a CDF onto a target system is typically used for internal

debugging purposes. Be aware that should the config.cdf contain additional problems

other than the patched model system issue, forcing the CDF could cause problems on

the target system from which there may be no recovery.

— Use the Update Installation process to update the patched model system to the next

version of the operating system, if the next version has been released, thereby bypassing

the patch issue.