Letting Ignite/UX gain control of a system
This can be done by either entering:
bootsys hostname on the Ignite/UX server
boot lan.server_ip_address install on the client
This process copies a memory only file system (INSTALLFS) and a kernel (INSTALL). If the contents of INSTALLFS need changing (e.g. the IP address of the Ignite/UX server changes), use install_adm to update it. e.g.
instl_adm -d > /tmp/cfg
instl_adm -f /tmp/cfg
instl_adm -T checks the syntax
instl_adm -c updates the LIF file
INSTALL and INSTALLFS are in /opt/ignite/boot .
/var/opt/ignite/INDEX contains the different install configurations that are available for installs. These entries are normally made up of several configuration files, including the default setting for that release of the O/S, custom configurations that override the default and extra software/packages that should also be installed.
Creating Configuration Files
The make_config and manage_index commands can be used to create new configuration files.
e.g. make_config -s /depot_location -c /var/opt/ignite/data/Rel_Brelease/location
will take the SD/UX depot at /depot_location from the local server and use it to create a configuration file in /var/opt/ignite/data/etc
manage_index -a -f /var/opt/ignite/data/Rel_B.release/location -c “Title of INDEX entry”
will add an entry for the newly created configuration file to clause “Title of INDEX entry” in /var/opt/ignite/INDEX.
Alternatively, the INDEX file can be manually edited.