Ignite-UX Reference (March 2010, B3921-90005)

ignite(5) ignite(5)
make_config -s server:/depots/compiler \
-c /opt/ignite/data/Rel_B.11.23/compilers_cfg
manage_index -a -f /opt/ignite/data/Rel_B.11.23/compilers_cfg
The depot server (in this example <server>) should be replaced with the server on
which you have the SD software. The make_bundles command must be run on
the same client the depot exists. If the depot is not on the Ignite-UX server, you may
need to copy the make_bundles command to the depot server and run it there.
Note: The make_config command will need to be rerun each time new software
is added or modified in the depots.
make_config constructs Ignite-UX config files which correspond to SD depots.
When an SD depot is used as part of the Ignite-UX process, it must have a config file
which describes the contents of the depot to Ignite-UX. This command may auto-
matically construct such a config file given the name of an SD depot on which to
operate. This command should be run when adding or changing a depot which will
be used by Ignite-UX.
manage_index is used to manipulate the /var/opt/ignite/data/INDEX
file. This utility is primarily called by other Ignite-UX tools but may also be called
directly.
For non-SD application software:
If the source is not an SD depot, the make_config command is not applicable.
You will need to create a unique config file that includes the non-SD software. A
sample of a config file that performs a non-core archive may be found at:
/opt/ignite/data/examples/noncore.cfg
The comments in this example file describe where to copy the file and what to
change in the file to make it reference your archive and work in your environment.
5. Run ignite to complete the configuration and start the process.
On the server execute /opt/ignite/bin/ignite. This will start the Ignite-UX server
program.
Complete the Configuration:
When the GUI display titled "Ignite-UX (host name)" appears after the Welcome
screen is dismissed, perform the following:
a) Choose Options: Server Configuration...
b) Look over both the Server Options and the Session Options to verify they
are suitable.
About the Screen: ‘Configure Booting IP Addresses’
Booting Clients: xx.xx.xx.xx to xx.xx.xx.xx
These IP addresses are used to initially boot the target clients. They are used until the client is
assigned one of the DHCP-assigned addresses. One address is required for each simultaneous
boot. Typically one to three are needed, depending on the usage.
DHCP Addresses: xx.xx.xx.xx to xx.xx.xx.xx
These IP addresses are used during the operating system download and application loading. These
addresses are in use for most of the Ignite-UX download to a target machine.
One address is required for each simultaneous download. You should set more, if the addresses
are to be assigned permanently.
DHCP Class ID
The unique name for the DHCP server that serves these DHCP Addresses. This is not necessarily
the install server.
4