HP Tru64 UNIX and TruCluster Server Version 5.1B-6 Patch Summary and Release Notes

Loading Firmware from a BOOTP Server
The fwupgrade command has been modified to allow the specified firmware update image to
be loaded from a BOOTP server in a connected network. This process must use the bootpd
daemon.
Create a symbolic link from the shipping location of bootpd to the expected location:
# ln -s /usr/opt/obsolete/usr/sbin/bootpd /usr/sbin/bootp
You must manually create the bootptab file on the server. The following is an example of how
to set up the bootptab file on the server for this procedure:
# Example bootptab file for BOOTP support
.default1:\
:hd=/install/firmware:\
:sm=255.255.255.0\
:gw=16.69.255.1:
#
tab:tc=.default1:ht=ethernet:ha=08002b86f234:ip=16.69.222.42:
bobafett:tc=.default1:ht=ethernet:ha=0008c73a5a47:ip=16.69.222.48:
#
In this example, the directory /install/firmware was created on the bootp server. This
directory must contain the firmware of the systems to be updated. The file names must match
the entry on the fwupgrade command line. The firmware files must have read permissions, that
is, 444.
You must edit the inetd.conf file so that the file name passed by fwupgrade is found by the
console firmware. Edit the line /etc/inetd.conf file on the bootp server to look like the
following:
tftp dgram udp wait root /usr/sbin/tftpd tftp -r /install/firmware
Enable bootpd to start by removing the comment symbol (#) from the beginning of the line in
the /etc/inetd.conf file;
bootps dgram udp wait root /usr/sbin/bootpd bootpd
See the fwupgrade(8), bootptab(4), and bootpd(8) reference pages for more information.
Changes to tar, pax, and cpio Behavior
When extracting or listing an archive using the tar, pax, or cpio commands, specifying a slash
(/) at the end of argument will cause the command to act upon the directory and not the contents
in the directory. For example:
# tar xvf filename.tar dir1/
When creating an archive with these commands, specifying multiple slashes will result in the
placement of one slash for any directory entry in the archive header. Previously, specifying
multiple slashes would put these slashes in the archive header. For example:
# tar cvf filename.tar dir1//////////
Specifying a single slash when creating the archive will cause tar, pax, or cpio to pick up all
of the directory's contents. For example:
# tar cvf filename.tar dir1/
Changes to vdump and vrestore Disallow Larger Record Sizes
The vdump and vrestore programs have been tuned to disallow block sizes greater than 64
KB blocks. This is to avoid forward compatibility problems. With the installation of this kit, the
valid range is 2 through 64 KB blocks.
Prior Release Notes 55