User's Guide

# Stop the kernel linker warning from printing # when compiling a new kernel
is_hppa {
env_vars += "LD_OPTS=+vnocompatwarnings"
}
How do I recognize if a disk exists or not from within a configuration
file?
It is easy to see if a disk exists or not within an Ignite-UX configuration file. For example:
( disk[0/1/0/8/0.15.0].size == 0 ) {
error += "Disk at 0/1/0/8/0.15.0 does not exist"
}
The previous example configuration excerpt adds an error message if the disk does not exist. This
allows you to create a configuration that will alert you when disks that should be there are not.
However, this same error keyword will prevent an actual install from occurring; so use this only if
it is an actual fatal problem.
If you want to be alerted conditionally if the disk does exist, the example changes to the following:
( disk[0/1/0/8/0.15.0].size != 0 ) {
...
}
You could use this logic to conditionally define a disk layout only if the disks that it refers to exist.
This would allow you to create unique disk layouts for various systems that have disks at different
hardware addresses.
The size of a disk that does not exist on the system should always evaluate to zero. However,
some disk arrays may present zero size disk LUNs. If there is a possibility of encountering this
issue then you should consider the following example as an alternative (note that a zero length LUN
is not be useful in a disk layout definition):
( (disk[0/1/0/8/0.15.0].model ~ ".") ) {
...
}
The logic inside the inner parenthesis tests whether the model string is set or not. The ~ does an
extended regular expression match and the "." means match (one of) any character. Using this
logic ensures that there is a disk LUN present at that address because it contains a model string so
the configuration within the braces is evaluated only if the disk does exist.
You can change the sense of the test by adding a logical not operator (!):
( ! (disk[0/1/0/8/0.15.0].model ~ ".") ) {
...
}
206