newinv(1) [ultrix 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)
Check Out this Related Man Page
kits(1) General Commands Manual kits(1) Name kits - generate setld format distribution kits Syntax /usr/sys/dist/kits key-file input-path output-path [ subset... ] Description The command produces subset images, inventories, and control files for an installation using the 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 destination direc- tory into which the kit information is to be placed. The command produces a subset image and a .image file in the output-path directory for each subset. In the instctrl subdirectory of output- path, produces an inventory file and a control file. Any subset control program for the subset is transferred to output-path/instctrl. An instctrl directory is created if none existed. Arguments key-file The path name 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. input-path The path name which specifies the top of a hierarchy of files. This hierarchy contains the files which are to be kitted into subsets. output-path The name of the directory to be used to store the subset image and data files produced by the command. subset... The names of individual subsets can be specified by optionally listing them on the command line. If they are specified, only those subsets will be kitted. The 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. Restrictions Any subset control programs to be provided with the kit must be located in a directory scps in the working directory where the program is invoked. If no subset control program is found for a subset, an empty one is created. Examples The following example shows the command used to 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 ULT400.k /var/kits/input /var/kits/output The next example shows the same usage, but specifies that only the ULTACCT400 subset is to be created. kits ULT400.k /var/kits/input /var/kits/output ULTACCT400 Diagnostics kits: key-file not found The program was unable to find the key-file specified on the command line. kits: input-path not found The program was unable to find the specified input-path. kits: output-path not found The program was unable to find the specified output-path. kits: cannot create instctrl directory. The program cannot create an instctrl directory under output-path. Check that the user has write permission to output-path. kits: key-file format error One of the NAME, CODE, VERS, MI or ROOT values in the specified key-file is either missing or has a null value. Inventory file pathname not found 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. Generating media creation information...failed. 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. No such subset in key-file subset subset 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. compression failed. status = status The compression option was specified in the key-file and an attempt to compress a subset failed. This should not happen. Run the program once more. Files temporary files. log of subset packaging activity See Also invcutter(1), tarsets(1), stl_comp(5), stl_ctrl(5), stl_image(5), stl_key(5), stl_mi(5), stl_scp(5), setld(8) Guide to Preparing Software for Distribution on ULTRIX Systems kits(1)