2 What must be DRD-Safe?

System administrators execute the drd runcmd command to install, remove, modify, and verify software on the inactive system image. The following entities must be DRD-Safe:

•The software deployment commands:

oswinstall o swremove o swmodify

oswlist

oswverify (without -F and -x fix=true options

•The control scripts for the software being installed, removed, or verified. Note that the configure script is not in this list. It does not need to be DRD-safe because it runs after the inactive system image is booted:

ocheckinstall

opreinstall o postinstall o checkremove o preremove o postremove o unconfigure

overify

•The commands and control_utils invoked (directly or indirectly) as part of control script execution within the runcmd environment

•The OE update scripts (HP-UX 11i v3 and later operating systems)

oupdate_prep

opre_update

Note:

The minimal release, or a subsequent release, of HP Software Distributor (SD) that is required to install the DRD DynRootDisk software product, provides swinstall,

swlist, swmodify, swremove, and swverify commands that are DRD-safe. The minimal release of SD required for DRD can be found on the DRD home page.

Note:

Though the update utilities support update paths from HP-UX 11i v1 to 11i v2 and from HP-UX 11i v2 to 11i v3, these OE updates are not supported using DRD.

To be DRD-safe, one basic guideline must be followed: All commands run in the runcmd environment must only access or modify the inactive system image and not access or modify the booted system image.