Ignite-UX Custom Configuration files

#ifdef LAN_SEGMENT_2
( lla[0/0/0/0] == "08000A654321" ) {
ip_addr[0/0/0/0]="10.0.2.45"
}
( lla[2/0/2] == "08000A654123" ) {
ip_addr[2/0/2]="10.0.2.46"
}
( lla[1/0/0/0] == "08000A654213" ) {
ip_addr[1/0/0/0]="10.0.2.47"
}
...
#endif
You can now use unifdef to create a configuration file for LAN segment one:
$ unifdef –t
73
-DLAN_SEGMENT_1 -ULAN_SEGMENT_2 lan.cfg
server="10.0.0.2"
netmask[]="255.255.255.0"
route_gateway[0]="10.0.1.1"
route_destination[0]="default"
disable_dhcp=true
( lla[0/0/0/0] == "080009654321" ) {
ip_addr[0/0/0/0]="10.0.1.45"
}
( lla[2/0/2] == "080009654123" ) {
ip_addr[2/0/2]="10.0.1.46"
}
( lla[1/0/0/0] == "080009654213" ) {
ip_addr[1/0/0/0]="10.0.1.47"
}
...
Note that unifdef is not a general C preprocessor; you must explicitly define or undefine
variables before they are evaluated in the input file. If you require more functionality than
unifdef provides, refer to m4(1).
Coping with auto_adm and boot changes in HP-UX
B.11.23
Because PA-RISC systems have two possible kernels that they may need to boot with the release of
Ignite-UX C.6.0, there needs to be some way to interact with the boot loader to boot the desired
kernel.
Two criteria must be met:
 The installation process must be capable of a non-interactive installation or recovery.
 The installation process must provide a mechanism for selecting a kernel version.
These changes were made to the initial system loader (ISL) to enable it to understand a new format
of AUTO file (this ISL is provided as part of Ignite-UX in the LIF file
73
The –t option treats the input as plain text rather than C style source code. Because this configuration does not look like
C style source code, always use the –t option.
155