Problem
I would like to know how to perform push-down software installations over the network.
Solution
This can be done using custom(ADM) (also known as the "Software Manager") from the command line.
The basic steps that need to be performed are outlined here (note that "pushes" cannot be done for the initial system load):
1. Create an "swadmin" account, giving it a password and home directory.
2. The server must have root equivalency on the client, so the server must be added to the client's root user's .rhosts file.
For example, for server "spamsco.london.sco.com" and client "sconan.london.sco.com" and entry should be placed in /.rhosts on the client ("sconan") that reads:
spamsco.london.sco.com3. For each of the products or components that you want to "push", do one of the following on the server:
(a) Install the software (using custom(ADM))or(b) Load the software (using custom(ADM))or(c) Place the software images in a directory4. Push the software to the client.
When installing from installed or loaded software, as the root user on the server system, type:
# custom -h <client> -p <product> -i [<components>] \
-N <server>[:<swadmin password>]When installing from software images, type:# custom -h <client> -p <product> -i [<components>] \
-N <server>[:<swadmin password>] \
-z <image directory on the server>If you don't supply the swadmin password on the command line,
custom(ADM) will prompt for it.This is an example for pushing SCO Wabi to "sconan" from "spamsco", where the password for the "swadmin" account on "spamsco" is "swadmin_pass":
# custom -h sconan -p SCO:WABI -i -N spamsco:swadmin_pass5. Once you have completed installing the software, you should consider removing root host equivalence between the client and the server (that is, remove /.rhosts), as this may lead to system security being compromised.
See also
custom(ADM), Chapter 17 of the SCO OpenServer Networking Guide.