Ignite-UX (IUX) Frequently Asked Questions (July 2013)

Q: Why does changing variable values in the "Additional" screen no
longer control non-final networking settings (which should propagate
to final networking settings) after updating to C.7.7?
A: Prior to the C.7.7 release, it was possible to set final networking
parameters (without using the "final" keyword) from the Additional
screen with logic such as this:
dns_nameserver[0] = "1.8.26.55"
dns_domain = "default.corp.com"
_corp_dns_prefix = {"domain1","domain2"}
_corp_dns_prefix help_text "Select DNS Domain and NameServer"
_corp_dns_prefix == "domain1" {
dns_nameserver[0] = "1.4.25.85"
dns_domain = "domain1.corp.com"
}
_corp_dns_prefix == "domain2" {
dns_nameserver[0] = "1.7.9.83"
dns_domain = "domain2.corp.com"
}
However with the inclusion of the fix for QXCR1000741225, this no
longer works. The better solution in this case is to use the "final"
keyword, which is the more correct way of specifying this anyway. So
the above logic would then look like this:
final dns_nameserver[0] = "1.8.26.55"
final dns_domain = "default.corp.com"
_corp_dns_prefix = {"domain1","domain2"}
_corp_dns_prefix help_text "Select DNS Domain and NameServer"
_corp_dns_prefix == "domain1" {
final dns_nameserver[0] = "1.4.25.85"
final dns_domain = "domain1.corp.com"
}
_corp_dns_prefix == "domain2" {
final dns_nameserver[0] = "1.7.9.83"
final dns_domain = "domain2.corp.com"
}
If the Additional screen is visited and one of these choices is
selected, then those final attributes will be applied. Otherwise the
default ones will be applied. The above logic will work with all
Ignite-UX releases, including C.7.7 and later. See instl_adm(4) for
more information on the final keyword.
=============================================================================
==
----------------------------------------
4. Recovery (make_tape_recovery & make_net_recovery)
----------------------------------------
4.1
Q: We tried running the recovery system option from a client booted in