stl_image(4) [osf1 man page]

stl_image(4)						     Kernel Interfaces Manual						      stl_image(4)

NAME

       stl_image - Software subset image data files

DESCRIPTION

       Each  software  product that is distributed as subsets for the setld(8) command has an associated image data file.  This image data file is
       created by the kits(1) utility.	The image data file's name consists of the product's unique 3-letter name with the  string  .image  for  a
       suffix.	The image data file contains one record for each subset in the kit.  Each record contains three fields separated by white space:

       Checksum     The modulo-65536 checksum of the subset file (after compression, if the file is compressed)

       Size	    The size of the subset file in kilobytes (after compression, if the file is compressed)

       Subset name  The product code, subset mnemonic, and version number

EXAMPLES

       The following example illustrates OAT.image, the image data file for a hypothetical kit: 15923	 70 OATDCB100 24305   400 OATDCBDOC100

RELATED INFORMATION

       Commands:  gendisk(1), gentapes(1), kits(1), setld(8)

       Documents:  Guide to Preparing Product Kits delim off

																      stl_image(4)

stl_inv(4)						     Kernel Interfaces Manual							stl_inv(4)

NAME

       stl_inv - setld inventory file format

DESCRIPTION

       Each  software  product	that  is distributed as subsets for the setld(8) command has an associated inventory file.  This inventory file is
       created by the kits(1) utility.	The inventory file's name consists of the product's unique 3-letter name with the string .inv for  a  suf-
       fix.   The inventory file contains one record for each subset in the kit.  Each record contains the following twelve fields in order, sepa-
       rated by TAB characters:

       Flags	 The per-file software management flag, a 16-bit unsigned integer

       Size	 The actual number of bytes in the file

       Checksum  The modulo-65536 checksum of the file.  Hard links, directories, FIFOs, and sockets have 00000 in this field.

       uid	 The user ID of the file's owner

       gid	 The group ID of the file's owner

       Mode	 The 6-digit octal representation of the file's mode

       Date	 The file's last modification date

       Revision  The version code of the product that includes the file

       Type	 A letter that describes the file:

       b    Block device

       c    Character device

       d    Directory containing one or more files

       f    Regular file.  For regular files with a link count greater than one, see file type l.

       l    Hard link.	There are other files in the same inventory which have the same inum.	The  first  of	these  files  in  ASCII  collating
	    sequence is listed in the referent field.

       p    Named pipe (FIFO)

       s    Symbolic link

       =    UNIX domain socket

       Pathname  The dot-relative (./) pathname of the file

       Link-to	 For file types l and s, the path to which the file is linked; for types b and c, an integer representing the major and minor num-
		 bers of the device; for all other types, none

       Subset name
		 The name of the subset containing the file

RESTRICTIONS

       Fields must be separated by TAB characters.

RELATED INFORMATION

       Commands:  setld(8)

       Functions:  stat(2)

       Documents:  Guide to Preparing Product Kits delim off

																	stl_inv(4)