tarsets(1) General Commands Manual tarsets(1)NAME
tarsets - subset kitting command file generator
SYNOPSIS
/usr/lbin/tarsets [-d] pathname
OPTIONS
Enable debugging. Debug trace diagnostics are written to ts.dbg in the current directory.
DESCRIPTION
The tarsets command is used by the kits utility to produce software kits for use with the setld(8) utility. The tarsets command reads sub-
set inventory records from standard input and writes a command procedure to standard output. This command procedure contains the commands
required to create subset images for the subset described in the input.
The pathname argument specifies the root directory for the file hierarchy containing the files to be kitted in the subset.
All error diagnostics are written to a file named stderr in the current directory.
RESTRICTIONS
The output command procedure produces multiple tar files. Each tar file has a goal size of 400 Kb. The command procedure is modified
automatically to produce a single subset image when the tarsets utility is called from the kits utility.
RETURN VALUES
The tarsets utility has successfully completed. A hard link referenced in the inventory cannot be found in the input hierarchy.
ERRORS
The input record on line n is not in subset inventory format. The input record for path1 contains a pointer to path2 in the referent field
and path2 does not appear in the inventory. This error indicates that path2 was deleted from the inventory after being created by the inv-
cutter command. These are obsolete messages and can be ignored. This is an informational message. The number j is the number of charac-
ters in the command written to the output to produce volume k.
FILES
Diagnostic output Debug diagnostic output
SEE ALSO invcutter(1), kits(1), setld(8)stl_inv(4) Programming Support Tools
tarsets(1)
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)