admpackage(1M) DG/UX R4.11MU05 admpackage(1M)
NAME
admpackage - manage DG/UX-style software packages
SYNOPSIS
admpackage -o load [ -qv ] [ -r release-area ] [ -f release-medium ]
[ package ... ]
admpackage -o setup [ -F ] [ [ -r release-area ] [ -c client-list ] [
package ... ]
admpackage -o install [ -qv ] [ -i ] [ -r release-area ] [ -f
release-medium ] [ -c client-list ] [ package ... ]
admpackage -o import [ -qv ] [ -r release-area ] [ package_directory
]
admpackage -o list [ -qvR ] -f release-medium
admpackage -o list [ -qv ] [ -O exact ] [ -r release-area ] [ package
... ]
admpackage -o list [ -qv ] -c client-list [ -O exact ] [ -r release-
area ]
DESCRIPTION
admpackage is used for loading and performing necessary setup of
DG/UX packages. All software products that come from Data General
for the AViiON series computers are considered to be DG/UX packages.
The software release format is a superset of that used for SunOS 4.0.
Operations
load Load the specified package(s) from the release-medium into
a release area on the disk. If no packages are specified
on the command line, and all is a valid selection, then all
packages on the release-medium will be loaded.
setup Execute the package's setup script(s), stored in the
specified release area, to prepare the package for use. If
no packages are specified, then all packages that have not
previously been set up will be set up.
install This operation combines the load and setup operations into
a single step. With the -i switch the operation combines
the import and setup operations into a single step. Note
that all selected packages will first be loaded (or
imported), then all selected packages will be set up. If a
package does not have setup scripts, then no action will be
taken for the setup step.
import A package client system can only import a package from a
server's <package_directory>. The package must be fully
installed on the package server before it can be imported.
This operation can only be used for packages that have been
structured to support import. The package_directory is a
part of the package's directory structure and is typically
located in /usr/opt name space. The package_directory>
contains the read-only, sharable portions of the package as
well as prototypes of the read-write, system specific files
needed for the package (typically the files that will
reside in the /etc directory) . The package client must
gain access to the package_directory> via NFS before using
the import operation. The package client can then use the
import operation to "load" copies of the prototype system
specific files from the package server. The import
operation is to the package client what load is to the
package server. A package supports import if it has a
read-only, sharable <package_directory> that contains a
/root.proto and/or a /usr.proto directory.
list The list operation has three forms. In the first form,
distinguished by the -f option, the operation will list to
the standard output the packages which exist on the
specified release-medium. For the second form, if no
options are specified, or only a release area is specified,
then the operation will list to the standard output the
packages which have been installed in a given release area.
A package is considered to be installed when it has been
loaded and set up. In the final form, distinguished by the
-c option, the operation will list packages that are loaded
but require set up for the specified list of operating
system clients. You may use MY_HOST or the output from
hostname(1C) for the client list if you want to list
packages on your host that require set up. For all forms
of this operation, the -q option is automatically enabled
unless the -v option is specified.
Options
-f release-medium
Specify the medium from which the packages will be loaded.
The default release-medium is obtained through
admdefault(1M). The medium may be the name of a tape
device or a directory.
-F Force setup for packages that have been set up already.
Use of this option is potentially dangerous. You should
use this option only when instructed to do so by the
package's documentation. When -F is specified, the package
or packages to be set up must be listed on the command
line.
-r release-area
Specify the release area into which the package is to be
(or was) installed. The default release area is PRIMARY.
-c client-list
Specify the list of operating system clients for which the
package is to be set up. This list must be a
comma-separated list of clients that are served by your
host. The default client list is MY_HOST.
-i Switch the install operation to combine the import and
setup operations rather than the load and setup operations.
-q Quiet. Print minimal information about the files on the
system or the release-medium.
-v Verbose. Print detailed information about the files on the
system or release-medium.
-O exact For the list operation, this option assures that only a
match of the package specified is listed. For example, if
you want a list of packages that are installed and you
specify "dgux" with the -O exact option, only the "dgux"
package is listed. Without the -O exact option, any package
beginning with the "dgux" string is listed (for example,
dgux, dgux.man, dgux_R310.p01).
-R Print release information for the release-medium itself in
addition to information about the files on the release-
medium.
Loading from Disk
The release-medium value may be a disk directory name instead of a
tape device name. When this is the case, admpackage expects to find
a table of contents file named 1.xdrtoc in that directory. This file
is the same file that would appear as the second file on a
distribution tape, and contains names of other images. These other
images must also appear in the disk directory with filenames composed
of the ``tape'' file number, a period, and the image name from the
table of contents file. For example, if the table of contents file
says that file 4 has the image ``tcpip__r.base'', then the directory
should contain a file named 4.tcpip__r.base.
DIAGNOSTICS
Warnings
- The load operation is requested and the tape contains a file
load destination that is not /, or a part of /usr or /opt.
- The load operation is requested and admpackage was unable to
update the root prototype directory.
- The load operation is requested and the database file for the
client being updated is missing.
- The setup operation is requested and the setup script failed.
The setup script should provide more specific information
regarding the failure.
Errors
- admpackage is unable to read or manipulate the release-medium.
- The release-medium does not contain a table of contents.
- admpackage is unable to create necessary temporary files. The
root file system is probably out of space.
- The table of contents found on the tape is in an invalid
format.
- The specified release-area does not exist or is invalid. The
user must create a release area before loading packages into
that release area (see admrelease(1M)).
Exit Codes
This section lists the possible exit codes and what they mean.
0 The operation was successful.
1 The operation was unsuccessful.
2 The operation failed due to access restrictions.
3 There was an error in the command line.
NOTES
You must have appropriate privilege to perform all operations except
list. For systems supporting the DG/UX Capability Option,
appropriate privilege is defined as having one or more specific
capabilities enabled in the effective capability set of the user.
See cap_defaults(5) for the default capabilities for this command.
On systems without the DG/UX Capability Option, appropriate privilege
means that your process has an effective UID of root. See the
appropriate_privilege(5) man page for more information.
For all of the operations that optionally take a package argument,
the key word all may be used to perform the operation on all of the
available packages. This rule does not apply to the load operation
when the release media specifically excludes the selection all.
SEE ALSO
admclient(1M), admdefault(1M), admrelease(1M), admtape(1M),
appropriate_privilege(5), cap_defaults(5), sysadm(1M).
Licensed material--property of copyright holder(s)