Installing HP-UX 11.0 and Updating HP-UX 10.x to 11.0 HP 9000 Computers Edition 1

Appendix C 273

Ignite-UX System Administration

Section 10: Installing NetScape as a Post-Conﬁguration Step

Section 10: Installing NetScape as a

Post-Conﬁguration Step

Here is a little more complicated example of using Ignite-UX post

installation scripts to load software on new installs. Netscape is one of

those tools which seems to have a new navigator every six months. Due

to the frequency of the changes, this tool may not make sense to include

on the “golden system”. Here is an example of adding Netscape

Navigator tool.

This example shows one way of accomplishing the task using a

post_config_script. Another way would be to create a software

selection (sw_sel) that would reference the tar archive, and then a

post_config_script (or post_config_cmd) associated with the

sw_sel that would be run only if the selection was picked for loading.

Using a sw_sel would have the advantage of making it appear in the UI

as just another software selection, and would have the sw_impact

statements to ensure sufﬁcient ﬁle system space. For more examples, see

the ﬁles in /opt/ignite/data/examples.

WARNING It is up to the individual administrators to ensure the Netscape

Navigator product is appropriately licensed prior to its

installation.

Step 1) Get Netscape Navigator

Netscape Navigator is typically pulled from one of the Netscape ftp

server sites. The pulled ﬁles are gzip compressed tar images with an

encoded name similar to:

netscape-v30-export.hppa1.1-hp-hpux.tar.gz

Step 2) Special Considerations for Netscape

In order to run Navigator, each user needs the correct network

preferences. Unfortunately, these preferences cannot be defaulted, and

must exist in every users $HOME/.netscape directory. To get around this

limitation, we have supplied a “run-netscape” script. Instead of running

“netscape”, the user can run a link to “run-netscape” which will install

the default preferences at ﬁrst invocation.