pdf(4)

NAME

pdf — Product Description File

DESCRIPTION

A Product Description File describes product files contained in the HP-UX operating system. It consists of a file containing a single line entry for each file described, where each entry contains the following fields:

pathname 
owner 
group 
mode 
size 
links 
version 
checksum 
linked_to 

Fields are separated by a colon (:), and contain the information indicated:

pathname: Absolute pathname of the file (starts with /). If pathname is preceded by ?, it is an optional file that may or may not be present on the system.
owner: Symbolic or numeric ID of the owner of the file.
group: Symbolic or numeric ID of the group of the file.
mode: Symbolic representation of file type and permission information as displayed by the ls -l command.
size: Size of the file in bytes. In the case of device special files, it is the major/minor number. Directory sizes are not recorded.
links: Number of hard links to pathname.
version: Numeric value of the revision of the file. Commands supporting PDFs determine this value by invoking the what command on the file and searching for a revision number (see what(1)). If no revision is found, ident invoked (see ident(1)). The version number recorded is the first one encountered. If no version number is found, the field is empty.
checksum: Result of the application of the Ethernet (and hence IEEE 802.3) CRC checksum algorithm to the file's contents.
linked_to: File to which pathname is linked, whether with a hard or symbolic link. If pathname is not a link, this field is empty.

Some commands (namely pdfdiff and pdfck) rely on the convention that one file in a set of hard links is considered the primary file, indicating no linked_to file in the PDF, while the remaining files in the set all indicate the primary file as the linked_to (see pdfdiff(1M) and pdfck(1M)). This convention prevents double counting in size calculations, and allows some efficiencies in algorithms for checking consistency of links.

Empty fields indicate a ``don't care'' status. Any field except pathname can be empty.

comment lines in the file begin with the percent character (%). The first line of the file is always the comment:

% Product Description File 

The second comment line is produced by the mkpdf command's -c option. For HP-UX files, this comment usually indicates the product name and release.

EXAMPLE

Here is an example product description file:

% Product Description File 
% fileset TEST, Release 1.0 
/usr/bin/basename:bin:bin:-r-xr-xr-x:2244:1:66.2:4066520052: 
/usr/bin/cat:bin:bin:-r-xr-xr-x:4740:1:66.2:2516588651: 
/usr/bin/ccat:bin:bin:-r-xr-xr-x:24576:2:66.12:330130894: 
/usr/bin/dirname:bin:bin:-r-xr-xr-x:1936:1:64.3:549465715: 
/usr/bin/grep:bin:bin:-r-xr-xr-x:11988:3:66.11:2104745188: 
/usr/bin/ls:bin:bin:-r-xr-xr-x:24576:6:66.3:312786007: 
/usr/bin/ll:::::6:::/usr/bin/ls 
/usr/bin/su:root:bin:-r-sr-xr-x:90112:1:66.2:3088851439: 
% total size is 160172 bytes. 
% total size is 158 blocks. 

WARNINGS

The checksum algorithm is different than that used by the 7.0 Release version of the commands.

Use of PDFs is discouraged since this functionality is obsolete and is being replaced with Software Distributor (see sd(4)).

AUTHOR

The specification of PDF is derived from an early draft proposal for Bill of Materials in IEEE POSIX P1003.2 (Draft 2). This proposal was later dropped from the standard. The implementation is by HP.

pdf(4)

Technical documentation

» Table of Contents

» Index

NAME

DESCRIPTION

EXAMPLE

WARNINGS

AUTHOR

SEE ALSO