Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

gentapes(8) [ultrix man page]

gentapes(8)						      System Manager's Manual						       gentapes(8)

       gentapes - produce distribution mag tape media

       /usr/sys/dist/gentapes [-{wv}] [hostname:]product_code special

       The  utility is used to produce MT9 or TK50 mag tape distribution media.  The utility searches for the product_code as provided by the user
       on the command line, plus the letters "TK" which is appended to the product code by the utility.  If  a	corresponding  kit  descriptor	is
       found  in  the  utility uses the information in the kit descriptor to copy files to the tape media mounted on tape drive special.  Once all
       files have been transferred, the tape is rewound and each file is verified by using the results of and comparing it to sums  given  in  the
       kit  image  file.   The utility can support multi-volume tape kits, and multiproduct tape kits.	See for information on how to set up these

       The optional hostname: is the name of a remote TCP/IP network machine that contains the kitcap file.  The utility will search on the remote
       machine for the product_code and use it for creating the media.	The colon (:) is a required delimiter for TCP/IP networks, and there is no
       space between the colon and the product_code.  For example, if the product code was ULT-2.2-V-BW, and the kitcap file to  be  used  was	on
       node "mynode", the proper syntax for this option would be

       The  product_code  is  a  user  defined code that is located in and describes the partition, directories, and subsets that make up a kitcap
       description.  It can be any set of numbers or letters and is usually formed in a way to have some meaning relative to the product  that	it
       describes.  For example, if the product name is MYPRODUCT and it is version 1, the product_code might be MYP010.

       The special argument is used to specify a special device such as /dev/nrmt?l.

       -w     Write only.

       -v     Verify only.

	      If neither option appears on the command line, the utility by default will write and then verify the files in the kit descriptor.

       You  must  be  a  superuser  to run this program.  If the optional hostname is used, you must be able to access files on the remote host as

       ra device special files

       Kit descriptor database

See Also
       sum(1), kitcap(5), genra(8)


Check Out this Related Man Page

kits(1) 						      General Commands Manual							   kits(1)

       kits - generate setld format distribution kits

       /usr/sys/dist/kits key-file input-path output-path [ subset...  ]

       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.

       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

       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.

       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.

       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

       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.

       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

Man Page