Usr sbin swinstall

Store a copy of a response file or other files created by a request script in catalog. Schedules a job for the given date when remote operations are enabled. One or more software objects to be installed. The target on which to install the software selections. You can change the behavior of this command by specifying additional command-line options when you invoke the command using the -x option or by reading predefined values from a file.

The following table shows the defaults and options that apply to swinstall. See Appendix A for more information about setting options and a complete listing and description of each option. This section provides examples of commands for installing software products. To start an install session via the command line, you must assemble any options if needed , host and source names, and software selections into a command string.

For example:. The swinstall command has a variety of patch management features, including a patch management dialog in the GUI. When updating files, swinstall removes the original files as they are updated. If an error occurs while swinstall is loading new filesets, the product being loaded is marked as corrupt, the original files are lost, and you must repeat the installation. They are not removed until all filesets within the product finish loading.

If swinstall terminates because of an error, you can correct the error then re-run swinstall. However, when installing to alternate root file systems, the host will not be rebooted. If a local installation entails a reboot, the system reboots the target and the controller, so there is no process left to report success or failure. SD-UX does not automatically reconnect to the target after a reboot.

To find out if a software product requires the local host to be rebooted, get a description of the software either from the Software Selection window, using the menu item Show Description of Software , or from the Analysis dialog using the Product Summary and Product Description buttons.

These codewords and customer IDs are provided to you when you purchase the software or receive it as update. HP lists them on the Software Certificate which is packaged with the software. SD searches the. SD-UX prompts you for these codewords or numbers prior to the installation of protected software. Since the purpose of this command is only to store codewords and customer IDs, the -p option runs the command in preview mode so that no actual software installation takes place.

This process uses the new install-sd command, which is described in Appendix C. Your installation may commonly having multiple versions of a software product installed at various hosts on the network. Multiple installed version let you:. Back out defective versions by removing the new version and reconfiguring the old version, if necessary. If set to false, installed or configured multiple versions that is, the same product, but a different revision, installed into a different location are not allowed.

While multiple installed versions of software are allowed, multiple configured versions are not recommended. Once multiple versions of software are installed into a location, you can manage them by specifying the product attribute in the software specification of SD-UX commands. This is as opposed to specifying other version attributes such as revision and architecture. This lets you install old and new versions of software at the same time and configure both versions if the software packaging supports it.

You can avoid unauthorized, privately installed versions of software by controlling access to the IPD and restricting the use of the swinstall tool. The automatic configuration and compatibility filtering that is part of the swinstall command is not performed when installing to an alternate root.

You can, however, perform configuration separately from installation by using the swconfig command. SD-UX normally filters out software products that are incompatible with any selected targets.

Compatible means that the architecture of the hardware matches that required by the software determined by the system uname attributes. It also means that the OS version is the proper one for the software. The actual check for incompatible software is performed during the selection phase. The Software Selection window shows only those products compatible with the hardware and OS of all target systems. The GUI displays all products on the source for selection.

During an OS update, for example, if a system has been installed as You can also specify these options at a fileset level. Features and Limitations. Optional GUI. Ability to perform kernel rebuilding or rebooting. Ability to run control scripts as part of the installation: Checkinstall Analyses each target to determine if the installation and configuration can take place. Preinstall Performs file operations such as removing obsolete files before installation of software files.

Request Requests an interactive response from the user as part of the installation or configuration process. Configure Configures installed filesets or products.

Postinstall Performs additional install operations such as resetting default files immediately after a fileset or product has been installed. Unpostinstall Undoes a postinstall script in case swinstall must initiate recovery during the installation process. Unpreinstall An undo preinstall script in case SD must initiate recovery during the install process. Software can be installed to alternate root directories.

Installing with the GUI. Select Source Provide the location of the software depot from which the software will be installed. Select Software Choose the software to install. Analysis Preview Analyze preview the installation to determine if the selected software can be installed successfully.

Installation Perform the actual software installation. Figure Specify Source Dialog. Optional To specify another host system, type a source host name, or: Click on the Source Host Name button. Choose a host name from the list. Highlight one of the depots. Figure swinstall Software Selection Window. Figure Analysis Dialog. How much disk space was available before installation,. How much will be available after installation,. How much space must be freed to complete the operation.

Search the object list. Re-analyze repeats the analysis process. Figure Disk Space Analysis Window. Ready There were no errors or warnings during analysis.

Ready with Warnings Warnings were generated during the analysis. Ready with Errors At least one product selected will be installed or copied. Communication failure Contact or communication with the intended target or source has been lost.

Excluded due to errors Some kind of global error has occurred. Disk Space Failure The installation will exceed the space available on the intended disk storage. Products selected only because of dependencies.

Figure Install Window. Logfile displays the logfile. File loading fails. Customization for kernel-related filesets fails. A tape change is needed if you are installing from multi-tape media. Installing from the Command Line. Installation Tasks and Examples. Updating to HP-UX 11i.

Installing Patches. Recovering Updated Files. Re-installing Software Distributor. Installing Multiple Versions. Let users migrate to newer software versions at their own pace. Installing to an Alternate Root. Compatibility Filtering and Checking. More options. Technical documentation. How do you start the program? This is one of those mystical Linux moments when you realize that you are a fish and this is not the water you are used to.

If you are using a graphical desktop KDE or Gnome , the good news is that your newly installed program probably also has a newly installed icon and entry in your programs menu.

The bad news is that the menu is so large and poorly organized on most systems that you may not be able to find it. On the other hand, if you were installing a server or a command line utility, you probably will not find it in your menu no matter how hard you look. You may first want to read about the Linux Virtual File System for some background.

This includes your login shell and basic utilities like ls. The contents of this directory are usually fixed at the time you install Linux. Programs you install later will usually go elsewhere read on. The original Unix makers had a thing for abbreviation. A typical desktop system will have many programs here. When you compile software from source code see Installing from Source , those install files are usually kept separate from those provided as part of your Linux distribution.

This is where you will find commands for optional system services and network servers.