Dynamic Root Disk A.3.13 * Release Notes (766141-001, March 2014)

Safe command list
The drd runcmd command is used to run safe commands on the clone. The safe commands listed
below apply to all DRD releases, unless otherwise noted:
• swinstall
• swremove
• swmodify
• swlist
• swjob*
• view
• kctune (version A.1.1 and later)
• kcmodule
• kconfig
• mk_kernel
*The swjob command can be used to view SD logfiles on the clone. It cannot be used to
schedule jobs for later execution on the clone.
Installation and removal of patches and products
The drd runcmd command can be used in conjunction with swinstall and swremove to install
or remove patches. Use of drd runcmd to install or remove a non-patch product requires that all
its filesets be marked DRD-safe. You can determine whether a fileset has been marked DRD-safe
with the following command:
swlist –l fileset –a is_drd_safe –s depot_name product_name
Each fileset will be displayed with “true”, “false”, or blank. Filesets marked DRD-safe will display
“true”. Filesets marked DRD-unsafe display “false”. Filesets that display neither (blank) are treated
as DRD-unsafe.
Use of SD TUI/GUI
When using the SD TUI/GUI with drd runcmd, you may see messages about building a kernel
or rebooting the system. These messages are not accurate; under no circumstances will using SD
under drd runcmd lead to a reboot, nor will SD under drd runcmd lead to a kernel build on
the running system.
Installation requirements
DRD is dependent on other patches and software. For more information see, “Required patches
and software” (page 13) section.
14 System and software requirements