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
newinv(1) General Commands Manual newinv(1)NAME
newinv - Updates distribution kit master inventory
SYNOPSIS
/usr/bin/newinv mi-file input-path...
OPERANDS
The pathname of the master inventory file to be processed. If no master inventory file exists, you must create an empty one before using
the newinv command. The name of the product hierarchy to be scanned for files belonging in the inventory. All files and directories found
below the input-path are processed as belonging in the inventory.
DESCRIPTION
The newinv command interactively maintains the master inventory files used for producing distribution kits in setld format. The program
updates the master inventory for a product when changes are made to the hierarchy of files that are to be packaged in the subsets which
constitute the product.
The product hierarchy is scanned to produce a list of component path names relative to input-path. The list of pathnames is processed
against the mi-file to produce a list of files that have been removed from the product hierarchy and a list of files that have been added.
The user is then given an opportunity to intervene and direct the inventory maintenance by editing these lists. The user is placed in the
editor with each list available for editing. The editor used is the one specified by the EDITOR environment variable. If EDITOR is not
set, vi is used. When editing the list of files that have been removed from the product, the user is expected to verify that the removals
were intentional and confirm the intent by removing the associated records from the file. When editing the list of added files, the user
is expected to provide options and subset information for each new file, transforming the elements of the list into master inventory
records.
To produce a new copy of the master inventory file, both of these lists are merged with the records for the files which existed in the pre-
vious version and are still included.
RESTRICTIONS
The default text editor, if not specified in $EDITOR, is /usr/ucb/vi.
Files in the product hierarchy cannot be excluded from the master inventory. Files can be blocked from being kitted in the final distribu-
tion kit by setting the subset field of the master inventory record to a minus sign (-).
ERRORS
The mi-file specified on the command line cannot be found. The input-path directory specified on the command line does not exist.
EXAMPLES
To update the hypothetical master inventory file OAT100.mi from the hierarchy beginning at /var/kits/input, type:
newinv OAT100.mi /var/kits/input
FILES
Backup copy of master inventory The list of files missing from the product The list of files new to the product Intermediate join file List
of all files in the product
SEE ALSO invcutter(1), kits(1), vi(1), setld(8)stl_mi(4)environ(5) Guide to Preparing Product Kits
newinv(1)