custom(ADM) 06 January 1993 custom(ADM) Name custom - install software products and components Syntax custom [ [ -d|-o|-s set ] options ] | [ -a [ packages ] ] [ -v ] [ -m device ] options = [ -i|-l|-r [ packages ] ] | [ -f [ files ] ] Description With custom you can manage the software installed on your system by selectively installing or deleting portions of the UNIX system or other products. custom is executable only by the super user and is either interactive or can be invoked from the command line with several options. custom has three levels of operation: Complete Product, Service, and Service Component. At the Complete Product level, the entire product distribution is installed, which can consist of several products. At the Service level, groups of products that comprise a functional area are installed. At the Service Component level, an individual product, its packages, or individual files are installed. For example, a Complete Product could consist of several Services. In turn, a Service Component would include a number of packages. Files are extracted or deleted in packages. A package is a collection of individual files. You can also install additional products. You can list the available packages by using the custom command as described in the next section. You can use custom in two modes; interactively and non-interactively. The mode invoked depends on the use of the options and arguments pro- vided. These are described in the following sections. Interactive usage For a completely interactive use of custom, enter: custom without any options or arguments. The custom main menu appears with the following options: Install Allows a product or system to be added. A window is first opened to select a ``New Product'', a system set or other previously installed products. A system set is a collection of packages listed in a permsfile entry for a product. For example, ``op2'' is the set flag for SCO Portfolio 2.0. When a new product is selected, you are given the choice of adding the ``Entire Product'', ``Packages'' or ``Files''. When ``Entire Product'' is chosen, custom calcu- lates which installation volumes (distribution media) are needed, then prompts for the correct volume numbers. If ``Packages'' is chosen, a list of all available packages in the currently selected set is displayed. Each line describes the package name, whether the package is fully installed, not installed or partially installed, the size of the package (in 512 byte blocks), and a one line description of the package contents. Multiple packages can be specified by marking them with the space bar. The selected packages will appear with asterisks. When executed, custom will prompt for insertion of the neces- sary volumes. (You cannot use custom to install the entire RTS package if that package is already partially installed. If this situation comes up, use fixperm(ADM) to determine which files are missing, and then use custom to install each file in- dividually.) If ``Files'' is chosen, you are prompted to select the package and then the filenames. custom then prompts for volumes. If a system set is selected, custom operates at the product level. You are given the option of installing the ``Complete Product'' (complete distribution), ``Services'' (a specific group of products), or ``Service Components'' (individual prod- ucts). Remove Deletes the correct files in the specified package/product. Select the product or package to be deleted just as you select a product or package to install. List Lists all files in the specified package or all packages in a product set. Quit Leaves custom. To specifically install a new product interactively, enter: custom -a without any arguments. This provides only the Install option functionality which is provided within the fully interactive invocation of custom. If an attempt is made to overwrite an already installed product or pack- age using this -a option, custom prompts you for confirmation before con- tinuing. Non-interactive usage To use custom non-interactively, you can choose to install an individual product or manage a system set. These are distinguished by the options and arguments used with custom. Options To install an individual product, enter: custom -a package(s) package(s) is an argument which is a package name(s) in the product which is installed non-interactively. If an attempt is made to overwrite an already installed product or pack- age using the -a option, custom prompts you for confirmation before con- tinuing. To manage all your software completely non-interactively, the following combination of options and arguments are required: a set identifier (-o, -d, or -s set) a command (-i, -r, -l, or -f) and either one or more package names, or filename(s) The syntax line must consist of the three sections identified above for a successful invocation of custom. If any information is missing from the command line, custom is invoked interactively and the missing data is prompted for. Only one of -o, -d, or -s set may be specified. These stand for: -o operating system -d development system -s set to install a specified set Only one of -f, -i, -l, or -r may be specified, followed by an argument of the appropriate type (one or more package names, or filename(s)). These options perform the following: -i install the specified package(s) -r remove the specified package(s) -l list the files in the specified package(s) -f install the specified file(s) The -m flag allows the media device to be specified. The default is /dev/install (which is always the 0 device, as in /dev/fd0). This is very useful if the system has a 5.25-inch drive on /dev/fd0 and a 3.5- inch floppy on /dev/fd1, and it is necessary to install from the 3.5-inch medium. For example: custom -m /dev/rfd1135ds18 this will override the default device and use the one supplied with the -m flag. The -v flag allows verbose output for installing and removing packages. For example, it gives information on command being run and on the size of the packages. ALL is an argument to custom which is recognized by custom to signify the entire product. This argument can be seen as a package option while in interactive mode. Limitations If you upgrade any part of your system, custom detects if you have a dif- ferent release and prompts you to insert the floppy volume that updates the custom data files. Likewise, if you insert an invalid product or a volume out of order, you will be prompted to reinsert the correct volume. Upon installation of the operating system, the RTS package is always entirely installed. Files /etc/perms/* See also df(C), du(C), fixperm(ADM), installpkg(ADM), xinstall(ADM) Standards conformance custom is conformant with Intel386 Binary Compatibility Specification, Edition 2 (iBCSe2); it is an extension to AT&T System V developed by The Santa Cruz Operation, Inc.