Ignite-UX (IUX) Document for Frequently Asked Questions (FAQ) (762793-001, March 2014) (Edition: 3)

6 General installation
Frequently asked questions
Following are the frequently asked questions in installation in general, which is a compilation of
all the available feedback from the users.
How does Ignite-UX estimate needed file system sizes? Does it do anything other than
add up the impacts statements?
Ignite-UX adds in minfree (normally 10%) to the amount required by the software impact.
You might have software bundles that have overlapping contents: filesets and/or files. The
make_config command makes sw_impact statements for each bundle without any special
handling the guard against over-counting when the bundles overlap.
For example, the Ignite-UX-11-XX bundles all overlap. Thus, when you install all of them using
Ignite-UX, it estimates too much space.
You must be able to add the sw_impact, of all the sw_sels that you are installing and be able
to calculate the required file system size.
When does Ignite-UX configure software?
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.
How do I set the client's final networking information?
This can be done from the System tab of the Ignite-UX GUI, or using the keywords in the
configuration files (For information, see instl_adm(4)).
I do not want to use DHCP, can I still have Ignite-UX automatically determine
networking information for all my clients?
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 additional entries in /etc/opt/ignite/instl_boottab is not required. In this case,
boot the clients using boot lan instead of boot lan install. Only clients known in /etc/
bootptab are capable 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 must review; see question 2.5
(Can an Ignite-UX server install clients on multiple subnets?) also.
How can I make software in a depot available for installations?
You must 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:
26 General installation