HP Tru64 UNIX Technical Updates for the Version 5.1B and Higher Operating System and Patches (February 2010)
Define the alternate/cloned boot member disk using wwidmgr console command for each
member:
>>> wwidmgr -show wwid
>>> wwidmgr -quickset -item x -unit y
>>> set bootdef_dev dga1.1001.0.1.2 <--- alternative member1 boot disk
Boot each member:
>>> boot
Installing V5.1B-4 to an Alternate Root (Jan. 2007)
To use the dupatch root option to install Version 5.1B-4 to an alternate root path, you must
first install the latest patch tools. To do this:
1. Download the Version 5.1-4 kit.
2. Extract the kit into a convenient directory.
3. Change directory to the one containing the kit and run dupatch. This automatically installs
the latest tools if they are not already installed on the system.
4. Select quit from the Main Menu.
5. Rerun dupatch with the root option to install Version 5.1B-4 to an alternate root path.
Version 5.1B-3 (Patch Kit 5)
The following notes pertain to Version 5.1B-3.
Script Displays Nonexistent Command Name to Remove Cluster Member (May 2005)
When installing a Tru64 UNIX patch kit using the no-roll procedure and a cluster member is
down, the noroll_versw script may display a message containing a nonexistent command
to be used for removing a cluster member.
This occurs if the patch kit installs a patch that requires the use of a version switch. In that case,
you would see a message similar to the following at the end of dupatch session:
Patch OSFPAT00074200510 has been identified as needing a version
switch. Once the following reboot is complete, please enter the
"/var/adm/patch/noroll/noroll_versw" command from any cluster member.
Because the noroll_versw script expects all members to be up, running it when a member
is down causes a message similar to the following to be displayed:
The noroll_versw command cannot continue because members 'member1'
of this cluster are not up. Please reboot these members before
re-attempting this command or remove the members using the
clu_remove_member(8) command
However, there is no clu_remove_member command. The message should refer to the
clu_delete_member member.
Version 5.1B-2 ( Patch Kit 4)
The following notes pertain to Version 5.1B-2 / Patch Kit 4.
Login Failure Possible with Rolling Upgrade and C2 Security Enabled (Mar. 2005)
Login failures may occur as a result of a rolling upgrade of on systems with Enhanced Security
(C2) enabled. The failures may be exhibited in two ways:
• With the following error message:
Can't rewrite protected password entry for user
• With the following set of error messages:
login: Ignoring log file: /var/tcb/files/dblogs/log.00001: magic number 0, not 8
login: log_get: read: I/O error
Can't rewrite protected password entry for user
14