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)
Check Out this Related Man Page
kits(1) General Commands Manual kits(1)NAME
kits - Generates setld format distribution kits
SYNOPSIS
/usr/bin/kits key-file input-path output-path [subset...]
OPERANDS
The pathname of the manufacturing key file which describes the product to be kitted. Unless optional subset arguments are specified, all
subsets listed in the descriptor section of the key-file are kitted. The pathname which specifies the top of a hierarchy of files. This
hierarchy contains the files which are to be kitted into subsets. The name of the directory to be used to store the subset image and data
files produced by the command. The names of individual subsets can be specified by optionally listing them on the command line. If they
are specified, only those subsets are kitted. The kits program assumes that all other subsets for the product have been kitted and that
their images are in the directory specified by output-path. The key file specified must contain descriptors for each of the optional named
subsets.
DESCRIPTION
The kits command produces subset images, inventories, and control files for an installation using the setld command. You need to know the
key file which describes the product to be built, a hierarchy from which the component files to be kitted are to be taken, and a destina-
tion directory into which the kit information is to be placed.
In the output-path directory, the kits command produces a subset image file for each subset and a product_code.image file listing all the
kit's subsets. In the instctrl subdirectory of output-path, kits produces an inventory file and a control file. The optional subset con-
trol program for any subset in the kit is transferred to output-path/instctrl. An instctrl directory is created if none existed.
RESTRICTIONS
Any subset control programs to be provided with the kit must be located in a directory named scps in the working directory where the kits
program is invoked. If no subset control program is found for a subset, an empty one is created.
ERRORS
The kits program was unable to find the key-file specified on the command line. The kits program was unable to find the specified input-
path. The kits program was unable to find the specified output-path. The kits program cannot create an instctrl directory under output-
path. Check that the user has write permission to output-path. One of the NAME, CODE, VERS, MI or ROOT values in the specified key-file is
either missing or has a null value. The master inventory file pathname specified in the MI entry of the key-file cannot be found. Verify
that the pathname is accessible from the current directory. There are no records in the master inventory file for a subset which is being
kitted. Check the master inventory file for correctness of content and format. A subset name specified on the command line does not have
a descriptor line in the key-file. Check the spelling of the subset name on the command line. Check the contents of the key-file. The
compression option was specified in the key-file and an attempt to compress a subset failed. This should not happen. Run the kits program
again.
EXAMPLES
Produce a kit using key file ULT400.k in the current directory to package files from the hierarchy /var/kits/input, and place the results
in /var/kits/output. kits OAT100.k /var/kits/input /var/kits/output
Produce a kit using key file ULT400.k in the current directory to package files from the hierarchy /var/kits/input, and place the results
in /var/kits/output, but create only the OATDCB100 subset. kits OAT100.k /var/kits/input /var/kits/output OATDCB100
FILES
Log of subset packaging activity
SEE ALSO invcutter(1), newinv(1), tarsets(1), setld(8)stl_comp(4), stl_ctrl(4), stl_image(4), stl_key(4), stl_mi(4), stl_scp(4) Guide to Preparing
Product Kits
kits(1)