Dynamic Root Disk A.3.12.* Release Notes

QXCR1001054745. The issue where drd rehost will not allow SYSINFO_HOSTNAME to
contain the "-" character has been resolved. Symptoms of the issue appear as
follows:
-------------------------------------------------
======= 06/29/10 16:26:50 MESZZ BEGIN Rehost System Image
(user=root)
(jobid=st-shpu8)
* Checking System Restrictions
* Validating Target to Be Rehosted
* Validating New System Personality
* The messages from validation of the system info file
"sethost_shpu8" are given below.
* To see additional messages, run with higher verbosity.
* WARNING: The invalid value SYSINFO_HOSTNAME=st-shpu8 is ignored.
ERROR: A non-empty value must be specified for SYSINFO_HOSTNAME.
* End of messages from validation of the system info file
QXCR1001051734. Prior to the fix for QXCR1001051734, drd sync treated all
non-zero return codes from list_expander (the utility that creates the
initial list of files to be synchronized) as warnings. In some cases, this
resulted in an empty list of files to be synchronized, but just a warning
return code from "drd sync." After this fix, the return code from
list_expander is always respected, and an error return code will cause "drd
sync" to fail.
QXCR1001050440. Prior to the fix for QXCR1001050440, the existence of
/etc/lvmpvg caused drd clone to fail. After the fix, drd clone succeeds.
QXCR1001041894. Prior to the fix for QXCR1001041894, DRD sync incorrectly
recorded files with special characters in the DRD registry. This caused the
registry to be unreadable, making subsequent "drd sync" operations fail.
After the fix, files containing special characters are handled correctly.
DRD version A.3.6 and A.3.7 contain fixes for the following defects:
QXCR1000894322. ACLs that are set on LVM volume mount points in the root
group will now be copied to the clone providing the mount point has a journal
filesystem.
QXCR1000933863. Signals (SIGINT, SIGQUIT, SIGHUP and SIGTERM) to 'drd runcmd'
will no longer have extraneous fsdaemon and swagentd processes running.
QXCR1000985412. Prior to the fix for QXCR1000985412, customers who had
release B.11.xx.3.4 or prior installed on the inactive image and B.11.xx.3.4
or above on the booted system could get an error similar to the following
when running "drd runcmd": "One or more postcommands for xxx failed." The fix
to QXCR1000985412 resolves this problem.
QXCR1001037278. With this fix, execution of 'drd umount' no longer creates a
file called 'mapfile' in the current directory on LVM root systems.
QXCR1001023408: The help messages displayed drd runcmd -? have been changed
to show that “drd runcmd” takes a DRD-safe command as an argument, and to
display the list of currently-supported DRD-safe commands.
QXCR1000801373: This was a defect in VxVM that affected DRD. Before this
issue was addressed, the drd clone command failed on a VxVM-managed system
with a root group volume name ending in another root group volume name. For