Software Distributor (SD-UX) Administration Guide HP-UX 11i v1, 11i v2, and 11i v3 (762797-001, March 2014)
Table Of Contents
- Software Distributor Administration Guide
- Contents
- HP secure development lifecycle
- About This Document
- 1 Introduction to Software Distributor
- SD-UX Overview
- SD-UX Concepts
- Using the GUI and TUI Commands
- The Terminal User Interface
- Starting the GUI/TUI Commands
- Window Components
- Opening and closing items in the object list
- Marking Items in the Object List
- Preselecting Host Files
- Software Selection Window
- Session and File Management—The File Menu
- Changing Software Views—The View Menu
- Changing Options and Refreshing the Object List—The Options Menu
- Performing Actions—The Actions Menu
- Getting Help—The Help Menu
- XToolkit Options and Changing Display Fonts
- Working from the Command Line
- 2 Installing Software
- Installation with swinstall
- Features and Limitations
- Installing with the GUI
- Installing from the Command Line
- Installation Tasks and Examples
- Updating to HP-UX 11i
- Installing Patches
- Recovering Updated Files
- Installing Software That Requires a System Reboot
- Using Software Codewords and Customer IDs
- Re-installing Software Distributor
- Installing Multiple Versions
- Installing to an Alternate Root
- Compatibility Filtering and Checking
- Software Selection Checking
- Configuring Your Installation (swconfig)
- Verifying Your Installation (swverify)
- Installation with swinstall
- 3 Managing Installed Software
- 4 Managing Software Depots
- Depot Management Commands and Concepts
- Copying Software Depots
- Registering and Unregistering Depots (swreg)
- Verifying Signed Software Signatures
- Additional Depot Management Tasks and Examples
- Combining Patch Depots
- Creating a Tape Depot for Distribution
- Setting Depot Attributes
- Creating a Network Depot
- Managing Multiple Versions of HP-UX
- Listing Registered Depots
- Listing the Contents of a Depot (swlist -d)
- Source Depot Auditing
- Verifying a Depot (swverify -d)
- Removing Software from Depots
- Removing a Depot
- 5 HP-UX Patching and Patch Management
- 6 Using Jobs and the Job Browser
- 7 Remote Operations Overview
- 8 Reliability and Performance
- 9 SD-UX Security
- 10 Creating Software Packages
- Overview of the Packaging Process
- Identifying the Products to Package
- Adding Control Scripts
- Creating a Product Specification File (PSF)
- Product Specification File Examples
- PSF Syntax
- PSF Object Syntax
- Selecting the PSF Layout Version
- PSF Value Types
- Product Specification File Semantics
- Re-Specifying Files
- Packaging the Software (swpackage)
- Packaging Tasks and Examples
- Registering Depots Created by swpackage
- Creating and Mastering a CD-ROM Depot
- Compressing Files to Increase Performance
- Packaging Security
- Repackaging or Modifying a Software Package
- Packaging In Place
- Following Symbolic Links in the Source
- Generating File Revisions
- Depots on Remote File Systems
- Verifying the Software Package
- Packaging Patch Software
- Writing to Multiple Tapes
- Making Tapes from an Existing Depot
- 11 Using Control Scripts
- Introduction to Control Scripts
- General Script Guidelines
- Packaging Control Scripts
- Using Environment Variables
- Execution of Control Scripts
- Execution of Other Commands by Control Scripts
- Control Script Input and Output
- File Management by Control Scripts
- Testing Control Scripts
- Requesting User Responses (swask)
- Request Script Tasks and Examples
- 12 Nonprivileged SD
- A Command Options
- B Troubleshooting
- Error Logging
- Common Problems
- Cannot Contact Target Host’s Daemon or Agent
- GUI Won’t Start or Missing Support Files
- Access To An Object Is Denied
- Slow Network Performance
- Connection Timeouts and Other WAN Problems
- Disk Space Analysis Is Incorrect
- Packager Fails
- Command Logfile Grows Too Large
- Daemon Logfile Is Too Long
- Cannot Read a Tape Depot
- Installation Fails
- swinstall or swremove Fails With a Lock Error
- Use of Square Brackets ([ and ]) Around an IPv6 Address Causes an Error
- Some SD commands do not work after network configuration changes
- C Replacing or Updating SD-UX
- D Software Distributor Files and File System Structure
- Glossary
- Index
Network depots offers these advantages over installing directly from media:
• Several users can pull software down to their systems (over the network) without having to
transport media to each user.
• Installation from a network server is faster than from media.
• You can combine different software products from multiple media or network servers into a
single depot.
Types of Depots
A depot usually exists as a directory location. This software is in a hierarchy of subdirectories and
filesets organized according to a specific media format. A host may contain several depots. For
example, a software distribution server on your network might contain a depot of application
software, a depot of patch software, and a depot of OS software.There are two types of depots:
directory and tape.
Directory Depot
• A directory depot consists of software stored under a special SD-UX-managed directory on
your file system, usually /var/spool/sw.
• A directory depot can be writable or read-only.
• When you use the SD-UX commands to refer to a directory depot, you need only to refer to
the depot’s top-most directory. In a CD-ROM depot, this directory would be the CD-ROM
mount point, such as /cdrom/mydepot.
Tape Depot
• Tape (serial) depots offer advantages when you must copy or install software over slow or
unreliable network connections, including the web. (First copy the depot to a local host, then
install from the local depot.)
• Software in a tape depot is formatted as a tar archive.
• Depots for actual cartridge, DAT and 9-track tape are referred to by the path to the tape
drive’s device file. For example: /dev/rmt/0m.
• You cannot modify or verify tape depots.
• You can create a tape depot only with the swpackage command. You cannot use swcopy
to copy software directly to a tape. See Chapter 10: “Creating Software Packages ” (page 165)
for more information on swpackage.
• Software in a tape depot must first be transferred to a directory depot before it can be accessed
by other hosts on the network.
• A tape depot can be accessed by only one command at a time.
Depot Registration
To make the software in a depot available for use by SD-UX commands across a network, you
must register the depot. You can also unregister a depot if you do not want it to be available. See
“Registering and Unregistering Depots (swreg) ” (page 93) for more information.
Copying Software Depots
The swcopy command copies software between depots. Software that is copied into a depot cannot
be used directly; it is placed there only to act as a source for installation and other SD-UX operations.
84 Managing Software Depots