SPECIAL INSTRUCTIONS FOR DIGITAL UNIX 4.0A Patch 737.00
WARNING! Binary Incompatibility If Using Inline Mutex Operations
    Applications using "inline" mutex operations, as described in the pthread.h
    header file, will need to RECOMPILE after installation of this patch. The
    instruction sequences for the pthread_mutex_unlock routine have changed.

    Please refer to the existing note in pthread.h entitled "NOTICE: inline
    function performance vs. binary compatibility" for more information.


SPECIAL INSTRUCTIONS FOR DIGITAL UNIX 4.0A Patch 737.00
WARNING! Database Binary Incompatibility If Using New mkpasswd -s Option
    When the number of /etc/passwd entries reaches up into the 30,000 to 80,000
    range, mkpasswd will sometimes fail to create a hashed (ndbm) database.

    This patch allows customers to create hashed passwd databases from large
    passwd files by using a new option (-s) to the mkpasswd command.  The -s
    option increases the block size of the database page file.

    For customers choosing to use the mkpasswd -s option to avoid this type of
    failure, a potential database/binary compatibility problem may arise.  If a
    customer application that accesses the password database created by mkpasswd
    is built statically (non-shared), that application will be unable to read
    from or write to the password database correctly.  This would cause the
    customer application to fail either by generating incorrect results or by
    possibly dumping core.  Any statically linked application would be affected
    if it directly or indirectly calls any of the libc ndbm routines documented
    in the ndbm(3) man page and then accesses the password database.  To remedy
    this situation, the customer would need to re-link the application.

    Customers who do not use the mkpasswd -s option will not see this database
    binary compatibility problem.


SPECIAL INSTRUCTIONS FOR DIGITAL UNIX 4.0A Patch 749.00
WARNING! Updates to /etc/ddr.dbase and /etc/ddr.db
    This patch modifies /etc/ddr.dbase and /etc/ddr.db.  A copy of the original
    files should be made before installing this patch. Refer to the Patch Kit
    Release Notes or the Patch Documentation for more information.


SPECIAL INSTRUCTIONS FOR DIGITAL UNIX 4.0A Patch 736.00
WARNING! Possible System Setup Change Required, syslog Behavior Change

    The security of the syslog facility has been enhanced in this patch. Unless
    the domain host name of a remote host is entered in the local file,
    /etc/syslog.auth, the local system will not log any syslog messages from 
    that remote host.

    If you install this patch (the secure version of syslogd) on a system, and 
    you have configured or intend to configure other hosts to forward syslog 
    messages to the system refer to the Release Notes or patch README 
    documentation for information on how to setup the system.