Patch Name: PHCO_20388 Patch Description: s700_800 10.20 pax(1) cumulative patch Creation Date: 99/11/19 Post Date: 99/12/08 Hardware Platforms - OS Releases: s700: 10.20 s800: 10.20 Products: N/A Filesets: OS-Core.UX-CORE Automatic Reboot?: No Status: General Release Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHCO_20388 Symptoms: PHCO_20388: For device special files with a concatenated major/minor value greater than pax's maximum small file size (0x7FFFFFFF - 2GB), pax fails with the following error message: /dev/XXXX > 2GB. Not Dumped. PHCO_16877: 1. Pax does not handle soft/hard links properly in ustar format if the file/link names have a length >= 100 characters. 2. Pax cannot restore soft links with a length > 100 characters in cpio format. 3. Pax does not restore hard links in cpio format. PHCO_11977: 1. pax with "-p e" or "-p o" incorrectly restores owner/group for file types other than regular files and directories. 2. pax may incorrectly restore hard links. 3. When pax cannot find the archive file specified on the command line, the following error messages are displayed: "pax: [offset 0m+0k+0]: No such file or directory" "pax: [offset 0m+0k+0]: Bad file number" "pax: Unable to determine the archive format." PHCO_11473: pax fails VSC4 tests for assertions 140, 1026 and 1028. PHCO_11145: pax -X does not work correctly. For two file systems (/mnt1 and /mnt2), the following pax command "pax -wXf /dev/rmt/0m /mnt1 /mnt2" should archive both file systems. However, it only archived /mnt1 and /mnt2's directory name but not /mnt2's contents. PHCO_10949: 1. For tar format archives, pax does not correctly handle file names with length >= 100. For directories, the name field gets null, resulting in tar (on extraction) thinking it is at end of archive, or pax (on extraction) incorrectly restoring those directories. For regular files, the mode gets appended to the file name on extraction. 2. For tar format archives, when the user wants to preserve the UIDs/GIDs on the archive, pax restores with UIDs/GIDs of invoking user if the uname/gname on the archive does not exist on the system. PHCO_10376: pax archive not restored correctly; tar tvf shows " /" in front of affected files. Defect Description: PHCO_20388: The concatenated major/minor value for device special files was incorrectly being range checked against pax's maximum small file size (0x7FFFFFFF - 2GB). PHCO_16877: 1. In ustar format, pax will fail to create a hard link, and the string "ustar" will be appended to the link target of any symbolic link where the target name is exactly 100 characters. There is no error message output to indicate to the user that the tar format of pax will not backup symbolic/hard links if the link target name is > 100 characters in length. 2. In cpio format, pax fill fail to create symbolic links if the link target name is > 100 characters in length. 3. In cpio format, pax fails to restore hard links; it creates regular files instead. PHCO_11977: 1. pax with "-p e" or "-p o" incorrectly restores owner/group for special files, which includes file types other than regular file and directory (character special, block special, fifo, symbolic link). pax assigns the owner/group to be that of the current process, rather than what is on the archive. Regular files and directories are restored correctly. 2. pax may incorrectly restore hand links. When creating an archive, pax uses a hash array and keeps linked lists of all hard links. The problem occurs when multiple inodes (which have hard links) hash to the same address; hash collisions are not handled correctly. Therefore, the problem does not always occur for all hard links, since hash collisions do not always occur. 3. When pax cannot find the archive file specified on the command line, the following error messages are displayed: "pax: [offset 0m+0k+0]: No such file or directory" "pax: [offset 0m+0k+0]: Bad file number" "pax: Unable to determine the archive format." pax is using a warning message routine which is intended for when a corrupt archive is encountered, where the offsets may be useful. A different routine should be used for when the archive file is not found. PHCO_11473: Fixes were made for pax to pass VSC4 tests. PHCO_11145: The current pax -X implementation did not take into account that more than one pathname (hence more than one device ID) can be specified on the command line. So, it sets the device ID to be checked from the beginning and it never changes. The fix is to reset the device ID for checking for each new pathname on the command line or stdin. PHCO_10949: 1. For tar format archives, pax does not handle correctly file names >= 100. For directories, the name field of the tar header ends up null. Then if the tar command is used for extraction, it hits the null and thinks it is at end of archive. If pax is used for extraction, it may incorrectly restore those directories. For regular files, if name >= 100, the mode (next header field) gets appended to the file name. 2. For tar format archives, when extracting a file with a UID/GID that cannot be found in /etc/passwd, pax restores the file with UID/GID of the invoking user, even when the user specifies "-p e" or "-p o". PHCO_10376: pax archive not restored correctly when minor number for file is 8 octal digits long. tar tvf shows an extra " /" in front of affected files. Unwinding the archive creates a directory called " " (space). SR: 8606105686 4701406967 5003358804 Patch Files: /usr/lib/nls/msg/C/pax.cat /usr/bin/pax /sbin/pax what(1) Output: /usr/lib/nls/msg/C/pax.cat: None /usr/bin/pax: $Revision: 78.6.1.19 $ PATCH_10_20: hpux_rel.o pax.o append.o buffer.o cpio .o create.o extract.o fileio.o hash.o link.o list.o mem.o namelist.o names.o pass.o path name.o replace.o tar.o ttyio.o warn.o charma p.o 99/11/19 /sbin/pax: $Revision: 78.6.1.19 $ PATCH-PHCO_18644 for 10.20; for 10.30, 11.x compatib ility libc.a_ID@@/main/r10dav/libc_dav/libc_ dav_cpe/9 /ux/core/libs/libc/archive_pa1/libc.a_ID Jul 8 1999 15:44:31 PATCH_10_20: hpux_rel.o pax.o append.o buffer.o cpio .o create.o extract.o fileio.o hash.o link.o list.o mem.o namelist.o names.o pass.o path name.o replace.o tar.o ttyio.o warn.o charma p.o 99/11/19 cksum(1) Output: 1299790370 6328 /usr/lib/nls/msg/C/pax.cat 1327739916 94208 /usr/bin/pax 1398871377 401408 /sbin/pax Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHCO_10376 PHCO_10949 PHCO_11145 PHCO_11473 PHCO_11977 PHCO_16877 Equivalent Patches: None Patch Package Size: 550 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHCO_20388 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHCO_20388.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHCO_20388. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. WARNING: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHCO_20388.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHCO_20388.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: None