Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

stl_mi(5) [ultrix man page]

stl_mi(5)							File Formats Manual							 stl_mi(5)

Name
       stl_mi - software distribution master inventory file format

Description
       The master inventory (mi) files are used by the subset kitting program when manufacturing subsets for installation with the utility.

       A master inventory file contains one record for each file in a product containing vendor-specified attribute information about each file in
       the kit.

       The master inventory contains ASCII data, one record per line.  Each record is composed of three fields, which must  be	separated  by  TAB
       characters.

       Here is a description of each of the fields:

       FLAGS	 This is an integer flags value. The two lowest bits of this flag are defined. All other bits are reserved for use by Digital.

		 Bit  0 of this flag is the precedence bit. Setting the precedence bit for a file indicates to that a new copy of this file is not
		 as important to the target system as a copy that is already there. This is used by when determining which files to restore to the
		 system  after	updating a subset. Files containing configuration information that can be modified after being installed are often
		 marked with this flag.

		 Bit 1 of this flag is defined as the volatility bit. It is used to indicate that the file will change after  being  installed	to
		 the  target  system  and that the changes do not indicate that the contents of the file have been corrupted.  When an application
		 requires a log file, it is often installed as a zero length file on the target system. Such log files are normally marked in  the
		 master inventory with bit 1.

       PATHNAME  This  is  the name of the file for which the record exists. The pathname in this field must begin with a leading period (.).  All
		 records in the file must be sorted in ascending order on this field. There cannot be two records in a master inventory that  rep-
		 resent the same file. The program enforces these requirements.

       SUBSET	 The  name of the subset to which the file belongs. A file can be distributed as part of one subset only. Files that share a gnode
		 (links) must be in the same subset. Files that are in the product hierarchy but are not distributed as part of any subset  should
		 have a dash (-) in this field.

Examples
       This example shows a section of the master inventory used to manufacture a release of the ULTRIX software:
       0    ./etc/newfs    UDTBASE040
       0    ./etc/zoneinfo/Poland    -
       0    ./usr/bin/passwd	UDTBASE040
       0    ./usr/diskless/dev/rrz2c UDTDL040
       0    ./usr/etc/lockpw	UDTBASE040
       0    ./usr/include/search.h   UDTBASE040
       0    ./usr/lib/cmplrs/cc2.0/ppu	  UDTBASE040
       0    ./usr/lib/libplotdumb.a  UDTPGMR040
       0    ./usr/lib/terminfo/2/2621-nl  UDTBASE040
       0    ./usr/lib/terminfo/a/altoh19  UDTBASE040
       0    ./usr/lib/terminfo/h/h19b	  UDTBASE040
       0    ./usr/lib/terminfo/t/tek4024  UDTBASE040
       0    ./usr/man/man1/capsar.1  UDTMAN040
       0    ./usr/man/man1/ptx.1     UDTMAN040
       0    ./usr/man/man2/listen.2  UDTMAN040
       0    ./usr/man/man3/endhostent.3n  UDTMAN040
       0    ./usr/man/man3/ldaopen.3x	  UDTMAN040
       0    ./usr/man/man3/ruserok.3x	  UDTMAN040
       0    ./usr/man/man3/tparm.3cur	  UDTMAN040
       0    ./usr/man/man5/tzfile.5  UDTMAN040
       0    ./usr/man/man8/secsetup.8	  -
       0    ./usr/sys/MIPS/BINARY/mc146818clock.o   UDTBIN040
       0    ./usr/sys/data/dhu_data.c	  UDTBIN040
       0    ./usr/sys/h/devio.h UDTBASE040
       0    ./usr/sys/io/uba/qduser.h	  UDTBIN040
       0    ./usr/sys/net/rpc/clnt.h UDTBIN040
       0    ./usr/var/dss/ncs/llbd   UDTRPCRT040

See Also
       invcutter(1), kits(1), iff(8), setld(8).
       Guide to Preparing Software for Distribution on ULTRIX Systems

																	 stl_mi(5)

Check Out this Related Man Page

newinv(1)						      General Commands Manual							 newinv(1)

Name
       newinv - update distribution kit master inventory

Syntax
       /usr/sys/dist/newinv mi-file input-path

Description
       The  command  interactively maintains the master inventory files used for producing distributions in format. The program updates the master
       inventory for a product when changes are made to the hierarchy of files which are to be packaged in the subsets which constitute the  prod-
       uct.

       The  product  hierarchy	is  scanned to produce a list of component path names relative to input-path.  The list of path names is processed
       against the mi-file to produce a list of those files which have been removed from the product hierarchy and a list  of  those  files  which
       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,  is  used.	 When editing the list of files which 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 record from the file. When editing the list of files  which	have  been
       added to the product, the user is expected to provide flags and subset information for each new file, transforming the elements of the list
       into master inventory records.

       Both of these lists are merged with the records for the files which have not been changed to produce a new copy	of  the  master  inventory
       file.

   Arguments
       mi-file	      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 command.

       input-path     The name of the product hierarchy to be scanned for files belonging in the inventory. All files and directories found  below
		      the input-path will be processed as belonging in the inventory.

Restrictions
       The default text editor if not specified in $EDITOR is

       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 NOSHIP.

Examples
       To update the master inventory file ULT400.mi from the hierarchy beginning at /var/kits/input, type:
	   newinv ULT400.mi /var/kits/input

Diagnostics
       newinv: where is mi-file?
       The mi-file specified on the command line cannot be found.

       input-path: bad directory.
       The input-path directory specified on the command line does not exist.

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
       kits(1), vi(1), stl_mi(5), environ(7), setld(8)
       Guide to Preparing Software for Distribution on ULTRIX Systems

																	 newinv(1)
Man Page