Software Distributor (SD-UX) Administration Guide HP-UX 11i v1, 11i v2, and 11i v3 (762797-001, March 2014)

If the superuser does have write permission on the remote file system and you set the
write_remote_files to true, swpackage creates the new depot and package products into
it.
The constraints for an existing NFS mounted depot are the same as when creating a new depot.
So, you must:
1. Set the write_remote_files option to true and
2. Make sure the superuser can write to the NFS file system to package a depot on an
NFS-mounted file system.
When these constraints are satisfied, the ACL protection mechanism controls operations on NFS
mounted depots the same way it controls operations on local depots.
Verifying the Software Package
If swpackage created a depot rather than storing the package in an existing registered depot,
you must register the depot with the swreg command. (See “Registering Depots Created by
swpackage ” (page 194).)
After the depot is registered, you can verify it with the swverify command. For example, to verify
the integrity of the product Pascal in the local default depot:
swverify -d Pascal
For more information about verifying depots, see “Verifying a Depot (swverify -d) ” (page 101).
You can also test the package by installing it on a system. For example, to install the package
named Pascal, located on the default depot /var/spool/sw in the host svrhost, onto the
primary root of a host named myhost:
swinstall -s svrhost Pascal @ myhost
(This example does not specify the depot location because it is assumed that the software is located
in the default /var/spool/sw on svrhost.)
For more information about verifying installed software, see “Verifying Your Installation (swverify)”
(page 57)
Packaging Patch Software
A number of software attributes are available to all software levels (bundles, products, subproducts,
and filesets) that permit packaging of patch software. For complete information on patch attributes
and a sample PSF, see Chapter 5: “HP-UX Patching and Patch Management” (page 102).
Writing to Multiple Tapes
When you package products to a distribution tape, the media_capacity option defines the size
of the tape media (in one million byte units). The default value for this option is
media_capacity=1330, which is the size of an HP DDS tape. If the target tape is not a DDS
tape, you must specify the media_capacity value.
NOTE: The capacity of the DDS tape is in one million byte units (1,000,000 bytes), not Mbyte
units (1,048,576 bytes). Most tape drive manufacturers specify capacity in one-million byte units.
If the products being packaged require more space than the specified media capacity, swpackage
will partition the products across multiple tapes.
To find out if multiple tapes will be required, swpackage will calculate the tape blocks required
to store the depot catalog and each product’s contents.
When multiple tapes are necessary, swpackage writes the entire catalog onto the first tape plus
any product contents that also fit. For each subsequent tape, swpackage prompts you for a “tape
is ready” response before continuing.
Packaging Tasks and Examples 199