Technical data

Chapter 1 25

Before You Install

Choosing the Install Source

5. You must edit the ﬁle /etc/instl_boottab on the server and add

at least one IP address that is reserved for booting install clients. The

IP addresses you add should be for cold installs only and should not

be used by any other systems. However, if you know the LAN Link

Addresses (LLA) of the systems you will be installing, you can use the

IP addresses of those systems, providing you append the keyword

"reserve". See the examples in the ﬁle /etc/instl_boottab for

more guidance.

6. If you want to boot multiple systems from the server at the same

time, you must add more than one IP address to this ﬁle. The server

may deny boot services if multiple systems try to use the same IP

address during booting.

Optional Install Server Conﬁguration Steps

After your install server is set up, you may want to create some default

parameters to make the process easier. Running the instl_adm

command on the server can do this.

For example:

Use instl_adm(1M) to set the default SD-UX server and depot as in the

following command line (where sd_server is replaced by the hostname of

the swinstall server, and /var/hpux_depot is the location of its software

depot):

instl_adm -s sd_server:/var/hpux_depot

You can also create a message that can be displayed to users during the

installation.

For example:

The instl_adm -a option can be given a ﬁlename that contains the

message or, if given a "—" (dash) as shown below, the command will

prompt you to type in the message followed by Ctrl-D "end-of-ﬁle". Adding

the -d option will cause the command to display the default information

after making the changes, as follows:

instl_adm -a - -d

The instl_adm(1M) utility can also allow the advanced user to set up

enough information to completely automate the installation. This is done

by specifying conﬁguration information as listed in the instl_adm(4) man

page.