Dynamic Root Disk: Quick Start & Best Practices

10
are DRD-safe; that is, they can be installed by the drd runcmd command to an inactive image
without affecting the booted system. The few patches that are not DRD-safe set the fileset attribute
is_drd_safe to false; for example firmware patches fall into this category. In the rare event that a
patch is released with the is_drd_safe attribute incorrectly set to true, that patch will be added to
the drd_unsafe_patch_list file.
Follow this procedure to determine if your drd_unsafe_patch_list file needs to be updated:
1. View the file at ftp://ftp.itrc.hp.com/export/DRD/drd_unsafe_patch_list. (You can open this URL in a
Web browser.) Determine the “last updated” date listed in the file and make a note of it.
2. On your active system image, view the “last updated” date listed in the
/etc/opt/drd/drd_unsafe_patch_list file and make a note of it.
3. Compare the dates from Step 1 and Step 2 and if the “last updated” date listed in the Step 1 file
is later than the date listed in the Step 2 file, then your installed drd_unsafe_patch_list file is out of
date and you need to continue to Step 4 (in this procedure) to update the file. (If the “last
updated” date listed in the Step 1 file is the same as the Step 2 file, then you do not need to
update the drd_unsafe_patch_list file and you are finished with this procedure.)
4. If your installed drd_unsafe_patch_list file is out of date and needs to be updated (to handle
potential new DRD-unsafe patches), go to the HP IT Resource Center FTP site (see Step A below) to
download the most recent drd_unsafe_patch_list file. This file is updated when any new patch is
determined to have the is_drd_safe flag incorrectly set to true.
Update the drd_unsafe_patch_list file as follows:
1. Download the ftp://ftp.itrc.hp.com/export/DRD/drd_unsafe_patch_list file to
/etc/opt/drd/drd_unsafe_patch_list on your active system image.
If you have not created a clone, then you are done with updating the drd_unsafe_patch_list
file and have finished this procedure. If you have created a clone, continue with Step B.
2. Because DRD uses the copy of the drd_unsafe_patch_list file on the inactive system image,
the copy on that image must also be updated. If there is a clone, mount the inactive system
image:
# /opt/drd/bin/drd mount
3. Copy the drd_unsafe_patch_list file to the inactive system image:
# /usr/bin/cp /etc/opt/drd/drd_unsafe_patch_list \
/var/opt/drd/mnts/sysimage_00*/etc/opt/drd/drd_unsafe_patch_list
Note:
If you download the file to a Windows system and then
copy it to an HP-UX system, DOS-type carriage-return line
feeds might be inserted into the file. To eliminate these
characters, use the dos2ux(1) command
.
DRD-Safe: Identifying Patches that will not be Installed in a drd runcmd Session
A preview operation can be used to help a system administrator determine if any patches from a
desired patch selection will not install in a drd runcmd session. For example, to see if any DRD-
unsafe patches will be rejected when installing from a patch depot, execute the following preview
command: