3 More Discussions You Might Find Interesting
1. Fedora
Hi everyone,
I know the following questions are noobish questions but I am asking them because I am confused about the basics of history behind UNIX and LINUX.
Ok onto business, my questions are-:
Was/Is UNIX ever an open source operating system ?
If UNIX was... (21 Replies)
Discussion started by: sreyan32
21 Replies
2. Linux
Hi,
I have created my VM lab on redhat linux, but giving me error after updating new yum repository, its asking me for subscription. I want want switch my redhat linux lab from VM, which linux open source will be best to perform admin commands and tasks??
If possible , please provide iso file... (2 Replies)
Discussion started by: Nats
2 Replies
3. UNIX and Linux Applications
Anyone know of a good open source Knowledge Base software for UNIX that can connect to an Oracle back end? (0 Replies)
Discussion started by: RJ45
0 Replies
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)