User's Guide

Understanding what is_net_info_temporary does
Ignite-UX differentiates temporary and permanent network settings with the use of the final keyword.
The final keyword is placed in front on networking attributes to indicate that they should apply to
the final system. This behavior can change based upon the value of the
is_net_info_temporary variable.
Information picked up from a DHCP/bootp server is placed into the configuration without the final
keyword. Configuration files may also define network configuration without the final keyword. This
configuration is treated in the same way as networking information picked up from a DHCP/bootp
server.
When is_net_info_temporary is set to true, only networking information with the final
keyword will be reflected in the network settings of the final system. When set to false (the default),
networking information without the final keyword can override networking information specified
with the final keyword.
To illustrate this, let’s look at an example. The following partial configuration shows two DNS name
servers defined for a system with the final keyword:
final dns_nameserver[0] = "10.1.1.10"
final dns_nameserver[1] = "10.1.1.30"
The entry from /etc/bootptab used to provide this system with network information when
booting over the network looks like:
ignite-defaults:\
ht=ethernet:\
hn:\
bf=/opt/ignite/boot/nbp.efi:\
bs=48
ig0001:\
tc=ignite-defaults:\
ha=0073217D1429:\
ip=10.1.1.119:\
sm=255.255.255.0:\
gw=10.1.1.1:\
ds=10.1.1.10 *** DNS server
When booted using this bootp entry, Ignite-UX adds the following entry into the configuration
automatically:
dns_nameserver[0] = "10.1.1.10"
With is_net_info_temporary set to false, the information Ignite-UX will write into
/etc/resolv.conf for the DNS name server is:
nameserver 10.1.1.10
However with is_net_info_temporary set to true, the configuration marked with final is used
instead:
203