Glossary

A structure, attached to a software object, that defines access permissions for multiple users and groups. It extends the security concepts defined by the HP-UX file system mode bits by allowing specification of the access rights of many individuals and groups instead of just one of each.

The agent (swagent) runs on the local host. It services all selection, analysis, execution and status requests.

SD-UX allows you to change the default location of a depot directory.

SD-UX allows you to change the location of a root directory to a directory that may eventually be the root of another system.

The second phase of a software installation, copy, or remove operation, during which the host executes a series of checks to determine if the selected products can be installed, copied or removed on the host. The checks include the execution of check scripts and DSA (disk space analysis).

An "attribute" which signifies the name of a previous version fileset used in the "Match-What-Target-Has" functionality. If the match_target option is set to true, the system will match the ancestor fileset name to the new fileset name.

This keyword defines the "architecture" attribute for the product object. It refers to the operating system platform on which the product runs.

A .o file that needs to be replaced in an existing archive using the "ar" command. Used for patch files.

An operation in which SD runs an interactive request script to get a response from the user. Request scripts can be run by the swask, swconfig, and swinstall commands.

Information describing a software object's characteristics. For example, product attributes include revision number, tag (name), and contents (list of filesets). Fileset attributes include tag, revision, kernel, and reboot. File attributes include mode, owner, and group. An essential part of the PSF, attributes include such information as the product's short name or tag, a one-line full name title or a one paragraph description of the object. Other attributes include a multi-paragraph README file, a copyright information statement and others.

Software that will be modified by a patch.

Packaging the source files and information into a product, and creating/merging the product into the destination depot/media.

A collection of filesets that are encapsulated for a specific purpose. By specifying a bundle, all filesets under that bundle are automatically included in the operation.

This is the area within a depot that contains all the information needed by SD-UX to understand the organization and contents of the products stored in the depot. It includes a global INDEX file and a directory of information for each product version in the depot. It is sometimes referred to as the catalog directory.

This keyword defines the "category" attribute for the product object. It refers to the type of software being packaged.

Compact Disc-Read Only Memory. One type of media. Essentially, it is a depot that resides on a CD-ROM.

See CD-ROM Media.

An optional, vendor-supplied script associated with a product or fileset that is executed during the swinstall analysis phase. The result returned by the script determines if the fileset can be installed or updated.

An optional, vendor-supplied script associated with a fileset that is executed during the swremove analysis phase. The result returned by the script determines if the fileset can be removed.

Usually refers to diskless server computer. SD-UX is often used from a diskless server to install software.

Command line user interface. All SD-UX commands can be run from the command line. See also GUI, TUI, and IUI.

The capability in swinstall to filter the software available from a source according to the host's uname attributes. Software products are created to run on specific computer hardware and operating systems. Many versions of the same products may exist, each of which runs on a different combination of computer hardware and operating system. The default condition for compatibility filtering in swinstall is to NOT allow selection and installation of incompatible software.

A software product that will operate on a given hardware system. Software that passes compatibility filtering for a local host. See Incompatible Software.

An optional, vendor-supplied script of checkinstall associated with a fileset that is executed by swinstall (or swconfig) after the installation of filesets is complete.

A special ACL (global_soc_template) that is used to create initial ACLs for depot and roots.

Optional, vendor- or administrator-supplied scripts that are run during swinstall and swremove. Includes checkinstall, preinstall, postinstall and configure scripts for swinstall; the checkremove, unconfigure, preremove, and postremove scripts for swremove; and the verify script for swverify.

The controller is the component of the SD-UX software management command that is invoked by the user on the local host.

This keyword defines the "copyright" attribute for the destination depot (media) being created/modified by swpackage. It refers to the copyright information that pertains to the software product.

A corequisite dependency requires another software object to be installed in order for the dependent fileset to be usable. See Dependency.

Critical filesets contain software that is critical to the correct operation of the host. Critical filesets are those with the reboot and/or kernel fileset flags. During the load phase, critical filesets are loaded and customized before other filesets.

The changeable values contained in the default option file (above) which are modified with the syntax swcommand.option=value.

The file /var/adm/sw/defaults (system level defaults) or $HOME/.sw/defaults (user level defaults), which contains the default options and operands for each SD-UX software management command.

A relationship between a fileset and another software object in which the fileset depends on the other object in a specific manner. Also used to identify the software object upon which the dependency exists: for example, if fileset A depends on fileset B, then B is a dependent or dependency of A. SD-UX supports corequisite and prerequisite dependencies.

A repository of software products and a catalog organized such that the SD-UX software management commands can use it as a source. The contents of a depot reside in a directory structure with a single, common root. A depot can exist as a directory tree on a SD-UX file system or on CD-ROM media, and it can exist as a tar archive on a serial media. All depots share a single logical format, independent of the type of media on which the depot resides.

A depot that is available for use as a source of software products. A depot source in directory format is identified by the path to a directory where a CD-ROM containing a depot is mounted, or the path to the root directory of a depot in the file system. A depot source in tar format is identified by the path to a tape device containing a tape media, or the path to a regular file containing a depot in a tar archive. A depot source in directory format can be remotely accessed as a network source through a swagentd server.

Vendor-defined descriptive attribute for products and filesets. A paragraph description of the product or fileset.

The Details Dialog allows you to obtain more information regarding the specific process and monitor its progress.

Where software application files are placed for further integration and preparation for distribution. Developer hosts assemble, organize and create product tapes or depots.

This keyword defines the "directory" attribute for the product object. The default, absolute pathname to the directory in which the product will be installed. Defines the root directory in which the product files are contained.

The directory on a target host where the depot is located. The default is /var/spool/sw.

This process determines if a host's available disk space is likely to be sufficient for the selected products to be installed.

Overwriting an installed version of software with an older version.

Ends the depot specification, no value is required. This keyword is optional.

A collection of files. The software object upon which most SD-UX software management operations are performed.

Graphical User Interface. The OSF/Motif ™ user interface provided with the swinstall, swcopy and swremove commands (compare to the CLUI or TUI).

A computer system upon which SD-UX software management operations are performed. See local host.

The ACL that is attached to, and controls access to, the host object.

Software products are created to run on specific computer hardware and operating systems. Many versions of the same products may exist, each of which runs on a different combination of computer hardware and operating system. Incompatible software does not operate on the host(s) because of the host's computer hardware or operating system. The default condition in swinstall is to disallow selection and installation of incompatible software.

An INDEX file defines attribute and organizational information about an object (for example, depot, product, or fileset). INDEX files exist in the depot catalog and the Installed Products Database to describe their respective contents.

An INFO file provides information about the files contained within a fileset. This information includes type, mode, ownership, checksum, size, and pathname attributes. INFO files exist in the depot catalog and the Installed Products Database to described the files contained in each existing fileset.

Defaults files, option files, software_selection files, target_host files and session_files that modify and control the behavior of the SD-UX software management commands.

A product that has been installed on a host so that its files can be used by end-users. Contrast with a product residing in a depot on a host's file system, sometimes referred to as an "available product."

Describes the products that are installed on any given host (or within an alternate root). Installed product information is created by swinstall, and managed by swremove. The contents of an Installed Product Database reside in a directory structure with a single common root.

A product attribute in the Installed Products Database (IPD) that allows the vendor to uniquely identify products with the same tag (name) or revision.

Installed Products Database.

This keyword defines the "is_locatable" attribute for the product object. Defines whether a product can be installed to an alternate product directory or not. If specified, the attribute is set to a value of TRUE. If not specified, the attribute is assigned a value of FALSE.

Interactive User Interface. All SD-UX commands can be invoked on the command line (command line user interface or CLUI). In addition, the swinstall, swcopy, swlist, and swremove commands offer an interactive Graphical User Interface (GUI) with windows and pull-down menus, or a text-based Terminal User Interface (TUI) in which screen navigation is done with the keyboard (i.e. using tab and character keys; no mouse). IUI is a generic term that can mean either the GUI or TUI.

A fileset that contains files used to generate the operating system kernel. During the swinstall load phase, kernel filesets are loaded and customized before other filesets.

A word (or statement) that tells swpackage about the structure or content of the software objects being packaged by the user. Packaging information is input to swpackage using a Product Specification File.

The third phase of a software installation or copy operation; when swinstall and swcopy load product files on to the host; and when swinstall performs product-specific customization.

The host on which an SD-UX software management commands are being executed. Equivalent to the administrative host.

A product that can be relocated to an alternate product directory when it is installed. (If a product is not locatable, then it must always be installed within the defined product directory.)

Each of the SD-UX software management commands record their actions in log files (the swlist command is an exception). The default location for the various log files is /var/adm/sw/<command>.log.

This keyword defines the "machine_type" attribute for the product object. The machine type(s) on which the product will run. (If not specified, the keyword is assigned a wildcard value of "*", meaning it will run on all machines.) If there are multiple machine platforms, you must separate each machine designation with a | (vertical bar).

In packaging software to a distribution tape, this phase actually copies the contents of the temporary depot to the tape.

See Software Media.

A swagentd daemon that makes products in a local depot available for swinstall and swcopy access. There can be multiple network sources from a single host, each one a different depot served by that host's single swagentd daemon. A network source is identified by the host name and depot directory.

Another name for client host. See Client.

This keyword defines the "number" attribute for the destination depot (media) being created/modified by swpackage. The part or manufacturing number of the distribution media (CD or tape depot).

Operating System.

In swpackage, reading the product_specification_file to determine the product, subproduct and fileset structure; the files contained in each fileset and the attributes associated with these objects.

Software designed to update specific bundles, products, subproducts, filesets, or files on your system. There are point patches and superseding (cumulative) patches. By definition, patch software is packaged with the is_patch attribute set to true.

Separate patches that patch separate parts of the same base fileset.

An optional, vendor-supplied script associated with a fileset that is executed by swinstall after the corresponding fileset has been installed or updated.

An optional, vendor-supplied script associated with a fileset that is executed by swremove after the corresponding fileset has been removed.

An optional, vendor-supplied script associated with a fileset that is executed by swinstall before installing or updating the fileset.

An optional, vendor-supplied script associated with a fileset that is executed by swremove before removing the fileset.

A prerequisite dependency requires another software object to be installed (configured) in order for the first fileset to be installed (configured). See Dependency.

In SD Security, the user (or host system, for agents making RPCs) who is originating the call.

Directories on diskless servers that contain the private files of the diskless clients.

In software security, the ACL used to initialize the ACLs protecting new products on depots that are created by the host.

The root directory of a product object, in which (nearly) all its files are contained. A user can change (relocate) the default product directory when installing a locatable product.

The input file used to define the structure and attributes of the products to be packaged by swpackage.

A depot can contain multiple versions of a product. Product versions have the same tag attribute, but different version attributes. See Multiple Version. An IPD supports multiple installed versions of a product. Installed product versions have the same tag attribute, but different version attributes and/or a different product directory.

Collections of subproducts and filesets. The SD-UX software object that directly relates to the software purchased by the user.

A "push" installation means that the administrator can, from a centralized point, simultaneously place one or several copies of the software onto each of several remote target hosts (that is, "single point administration").

This keyword defines the "readme" attribute for the product object. A text file of the README information for the product; either the text value itself or a file name that contains the text.

The scope of the authority by which the Principal is authenticated in software security.

Or Registration. Determines which hosts are available for tasks (that is, which hosts have a daemon running). Also determines what depots are on a given host. Registration information consists of the depot or root's identifier (its path in the host file system). This information is maintained by the daemon which reads its own file at start-up.

An interactive control script that gets a response from the user. A request script prompts the user for a response, reads the user's answer, and stores the results in a response file. Request scripts can be run by the swask, swconfig, and swinstall commands.

A file that is generated by an interactive request script and contains the user's response.

This keyword defines the "revision" attribute for the product object. The revision information (release number, version) for the product.

The directory on a target host in which all the files of the selected products will be installed. The default (/), can be changed to install into a directory that will eventually act as the root to another system. See Alternate Root Directory.

The first phase of a software installation, copy, or remove operation, during which the user selects the software products to be installed on, copied to, or removed from the host.

A system on the network that acts as a software source for other nodes or clients on the network. Can be a network server or diskless server.

Each invocation of an SD-UX software management command defines a session. The controller automatically saves invocation options, source information, software selections and host selections in special file locations before the operation actually starts.

Directories located on a diskless server that are the location of operating system or application software that is shared among the system's diskless clients.

A system that contains one or more software products that can be installed on other systems. See Depot.

The term used to describe the objects that are packaged, distributed, installed and managed. The software filesets.

The second window to appear in the GUI. Helps you select the software or data files you want to install, copy or remove.

The term used to reference a depot being used as the source of a swinstall or swcopy operation.

See Software Source.

An optional grouping of filesets, used to partition a product which contains many filesets or to offer the user different views of the filesets.

Patches that supersede all previous patches to a given fileset.

A software product that provides all of the SD-UX functionality. SW-DIST is included on your HP-UX 10.X Core OS Disk or Tape. If SW-DIST is damaged, missing, or corrupted on your system, you will NOT be able to install or copy any HP-UX software that is packaged in the SD-UX format, including a new SW-DIST product.

The SD-UX command that allows you to modify Access Control List permissions that provide software security.

The daemon that provides various services, including initiation of communication between the controller and agent, and serving one or more depots simultaneously to multiple requesting agents on the host.

The SD-UX command that allows you to run an interactive request script to get a response from the user. Request scripts can also be run by the swconfig and swinstall commands.

The SD-UX command that configures software that has been installed, to make the software ready for use.

The SD-UX command that copies software from any software source to a depot. The swcopy command can add products to an existing depot, replace products already on a depot and create a new depot.

The SD-UX command that lets you install the new SW-DIST product from new SD media when you are updating the operating system. swgettools is necessary because the new media format may be different from the SD product that is already installed on the host system. This command is loaded from the new SD media using cp, rcp or tar.

The SD-UX command that installs or updates software.

The SD-UX command that lists software objects, their attributes and their organization. It lists both installed software and software contained within a depot.

The SD-UX command that allows you, from the command line, to change or add to the information in the IPD or depot catalog files.

The SD-UX command used by a software supplier or system administrator to organize software products and package them into a depot. The depot can be accessed directly by the SD-UX software management tools, it can be mastered onto a CD-ROM depot, or it can be made available to other hosts by the swagentd command.

The command SD-UX uses to register depots.

The SD-UX command that removes software that is installed, or software contained with a (writable) depot.

The SD-UX command that verifies (for correctness and completeness) software that is installed, or software contained within a depot.

Computers, either stand-alone or networked to other computers.

This keyword defines the distribution.tag or product "name" attribute for the destination depot (media) being created/modified by swpackage.

The software in a tape depot is formatted as a tar archive. Encoded in this archive is the same SD media format directory hierarchy that is used in a directory depot. Tape depots such as cartridge tapes, DAT and 9-track tape are referred to by the file system path to the tape drive's device file.

One type of software media. It uses tar to store software products and control files needed by the SD to use the media. It usually resides on a serial media such as a DDS, cartridge, nine-track, or other tape, though it can also be a regular file that contains the tar archive. Within the tar archive, directory and file entries are organized using the same structure as any other depot.

A tape media being used as a source of software products. A tape source is identified by the name of the special file used to access the device where the media resides, or by the name of a regular file that contains the tar archive.

A directory on a host in which software is installed, copied or removed. They can operate on either a target root directory or a target depot.

A one-line, full name attribute that further identifies the product.

Terminal user interface. A character-based display that works on a ASCII terminals and uses the keyboard to navigate (no mouse). See also CLUI, GUI, and IUI.

When a target is contacted for a software management operation, the system's four uname attributes - operating system name, release, version and hardware machine type - are obtained. Used to determine software compatibility with the proposed host.

An optional, vendor-supplied script associated with a fileset that is executed by swremove before the removal of filesets begins.

Overwriting software objects already installed on the system and replacing them with new objects.

This keyword defines the vendor's "uuid" attribute for the vendor object. Useful for NetLS vendors and for those who want to select products from two vendors who have chosen the same vendor_tag.

If a vendor specification is included in the PSF, swpackage requires the "vendor" and "tag" keywords.

Associates the product or bundle with the last-defined vendor object, if that object has a matching tag attribute.