Ignite-UX Frequently Asked Questions

A: Ignite-UX adds in minfree (normally 10%) to the amount required by
the software impact.
You may have software bundles that have overlapping contents:
filesets and/or files. The make_config command makes sw_impact
statements for each bundle without doing anything special to guard
against over-counting when the bundles overlap.
For example, the Ignite-UX-11-XX bundles all overlap so when you
install all of them using Ignite-UX it estimates too much space.
You should be able to add the sw_impact of all the sw_sels that you
are installing and to calculate the required file system size.
===============================================================================
5.2
Q: When does Ignite-UX configure software?
A: The Software Distributor configuration and Ignite-UX
"post_config_cmd" and "post_config_script" scripts are run after all
software has been installed and the client has booted the final
kernel from the target disk.
===============================================================================
5.3
Q: How do I set the client's final networking information?
A: This can be done from the "System" tab of the Ignite-UX GUI, or using
the keywords in the configuration files (refer to instl_adm(4)).
===============================================================================
5.4
Q: I do not want to use DHCP, can I still have Ignite-UX automatically
determine networking information for all my clients?
A: Yes. If you want more control over the allocation of IP addresses
and their mappings to your clients, you can configure entries in
/etc/bootptab for each client. Because BOOTP is a subset of DHCP,
the client's request for a DHCP server is satisfied with the BOOTP
response.
If you also specify a boot file (bf) of /opt/ignite/boot/boot_lif in
the bootptab entries, then you do not need any additional entries in
/etc/opt/ignite/instl_boottab. In this case, you would then boot the
clients using "boot lan" instead of "boot lan install". Only clients
known in /etc/bootptab would be able to boot if you do not use
instl_boottab.
sysname:\
hn:\
vm=rfc1048:\
ht=ether:\
ha=080009352575:\
ip=15.1.51.82:\
sm=255.255.248.0:\
bf=/opt/ignite/boot/boot_lif
Note: There is a known problem using this mechanism that you should
review; see question 1.6 (Using bootptab entries to satisfy the
DHCP request does not work. Why?) also.
===============================================================================
5.5
Q: How can I make software in a depot available for installations?
A: You should change to the release directory that is appropriate for
the software in the depot, then run make_config against the depot.
After the configuration is created, run manage_index to make it
visible in the Ignite-UX GUI. For example, for the following
situation:
SD depot machine: sdsource
SD depot: /var/application_depot
For release: 11.23
You would execute the following:
# cd /var/opt/ignite/data/Rel_B.11.23
# make_config -s sdsource:/var/application_depot -c app_name.cfg
# manage index -a -f /var/opt/ignite/data/Rel B.11.23/app name.cfg \