Red Hat NETWORK SATELLITE 5.1.0 - CHANNEL MANAGEMENT, Reference Manual

Page: 215 / 300

# solaris2mpm RHATrpush-3.1.5-21.pkg RHATrpush-3.1.5-23.pkg
Opening archive, this may take a while
Writing out RHATrpush-3.1.5-21.sparc-solaris.mpm
Opening archive, this may take a while
Writing out RHATrpush-3.1.5-23.sparc-solaris.mpm
Because no other directory was specified, the resulting .mpm files are written to the /tmp/
directory. Note that the name of the resulting .mpm files includes the architecture of the client on
which it was created. In this case, this was Sparc Solaris. The general format of mpm file names
is:
name-version-release.arch.mpm
Patch clusters are "exploded" — .mpm files are generated for each patch in the cluster, as well
as a top-level "meta" .mpm file containing information about the cluster as a whole.
Below are the options of solaris2mpm:
Option Description
--version
Displays the program's version number and exits
-h, --help
Displays this information and exits
-?, --usage
Prints program usage information and exits
--tempdir=<tempdir>
Temporary directory to work from
--select-arch=<arch>
Selects the architecture (i386 or Sparc) for multi-arch
packages.
Table 9.1. solaris2mpm options
4.2.1.2.
rhnpush
with .mpm Files
The Solaris version of
rhnpush
works like the standard utility, but with the added ability to
handle .mpm files. Below is a usage example:
% rhnpush -v --server testbox.example.com --username myuser -c solaris-8 \
RHATrpush-3.1.5-*.mpm
Red Hat Network password:
Connecting to http://testbox.example.com/APP
Uploading package RHATrpush-3.1.5-21.sparc-solaris.mpm
Uploading package RHATrpush-3.1.5-23.sparc-solaris.mpm
Obtaining Updates
201