invcutter(1) General Commands Manual invcutter(1)Name
invcutter - generate subset inventory files
Syntax
/usr/sys/dist/invcutter [ -d ] [ -f root-path ] [ -f version-code ]
Description
The command reads master inventory records from standard input. A subset inventory record is written to standard output for every record
read from the input. The information contained in the output record is derived from the input record and the file attribute information in
the file hierarchy rooted in the current directory.
Options-d Enable debugging. No useful diagnostics are printed.
-f root-path Specify an alternate root path for finding file attribute information.
-v version-code Specify a 3-digit version code for use in the version field of the output records. The default version code is 010.
Restrictions
All input records must be sorted in ascending order on the pathname field.
Files described in an input record which exist as sockets in the file hierarchy are not processable.
If a file is described in an input record has a link count greater than 1, all other links to the file must be represented in the input.
Examples
The following command will generate inventory records for the master inventory entries in PDS020.mi containing version fields set to 020:
invcutter -v 020 < PDS020.mi
Return Values
An exit status of 0 is returned if all goes well. An exit status of 1 is returned if an error occurs. See Diagnostics.
Diagnostics
"cannot chdir to pathname (error-message)"
The program cannot change directories to the pathname directory specified with the -f option. The error-message will provide additional
information.
"sort error, record #n"
The nth input record is not in the correct sort order. All input records must be in ascending ASCII colating sequence on the pathname
field.
"cannot stat filename (error-message)"
An error has occurred attempting to read the attributes of filename. The error-message explains exactly what happened.
"pathname: illegal file type code 0140000"
The file pathname is a socket. Sockets are not supported as valid file types for distribution.
"unresolved nlink n: pathname"
This indicates that file pathname in the master inventory is linked to n files which do not appear in the master inventory. Check inventory
for validity with the program.
"n unresolved hard links"
This is an informational message stating how many files were detected in the input inventory which had unresolved links.
See Alsonewinv(1), stl_inv(5), stl_mi(5)
Guide to Preparing Software for Distribution on ULTRIX Systems
invcutter(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)