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)
Check Out this Related Man Page
stl_mi(4) Kernel Interfaces Manual stl_mi(4) NAME
stl_mi - Software distribution master inventory files DESCRIPTION
Each software product that is distributed as subsets for the setld(8) command has an associated master inventory file. The master inventory file's name consists of the product's unique 3-letter name and a 3-digit version number with the string .mi for a suffix. The master inven- tory file is used by the software kitting program kits(1) in producing software distribution packages. A master inventory file contains one ASCII record, describing vendor-specified attribute information, for each file in the product kit. Each record is composed of three fields which must be separated by TAB characters. The fields are: A 16-bit unsigned integer. Bit 1 is the v (volatility) bit; when it is set, changes to the existing copy of the file can occur during kit installation. It is usually set for log files required by applications. The remaining bits are reserved. Possible values for this field are therefore 0 or 2. The dot-relative (./) pathname of the file described by this record. Each pathname must appear only once in the master inventory file. Pathnames must begin with a period (.). Records must be sorted in ascending ASCII sequence on this field. The name of the subset containing the file. Standard system directories are not included in subsets; they are represented by the keyword RESERVED in place of a subset name. Files that exist in the product hierarchy but are not distributed as part of any subset have a minus sign (-) in this field. Files that share a gnode (links) must all be included in the same subset. EXAMPLES
This example shows a section of the master inventory for a hypothetical layered product kit: 0 . RESERVED 0 ./usr/opt RESERVED 0 ./usr/opt/OAT100 OATDCB100 0 ./usr/opt/OAT100/bin OATDCB100 0 ./usr/opt/OAT100/bin/attr OATDCB100 0 ./usr/opt/OAT100/bin/dcb.spr OATDCB100 0 ./usr/opt/OAT100/bin/dcb_defaults OATDCB100 0 ./usr/opt/OAT100/bin/dcb_diag.sed OATDCB100 0 ./usr/opt/OAT100/bin/docbld OATDCB100 0 ./usr/opt/OAT100/bin/unstamp OATDCB100 0 ./usr/opt/OAT100/lib OATDCB100 0 ./usr/opt/OAT100/lib/br OATDCB100 0 ./usr/opt/OAT100/lib/br/README.dcb OATDCB100 0 ./usr/opt/OAT100/lib/br/attr.1 OATDCBDOC100 0 ./usr/opt/OAT100/lib/br/dcb.ps OATDCBDOC100 0 ./usr/opt/OAT100/lib/br/docbld.1 OATDCBDOC100 0 ./usr/opt/OAT100/lib/br/docbld.5 OATDCBDOC100 0 ./usr/opt/OAT100/lib/br/unstamp.1 OATDCBDOC100 0 ./usr/opt/OAT100/lib/doclib OATDCB100 0 ./usr/opt/OAT100/lib/doclib/templates OATDCB100 0 ./usr/opt/OAT100/lib/doclib/templates/conv.braces OATDCB100 0 ./usr/opt/OAT100/lib/doclib/templates/conv.command OATDCB100 . . . RELATED INFORMATION
invcutter(1), kits(1), newinv(1), setld(8) Guide to Preparing Product Kits delim off stl_mi(4)