Technical data

5. Creating the fli4l Archives/Boot media
If all configuration is completed, the fli4l archives/boot media may be created as either bootable
Compact-Flash, a bootable ISO image, or only the files needed for a remote update.
5.1. Creating the fli4l Archives/Boot media under Linux or other
Unix derivatives and Mac OS X
This is done by using scripts (.sh), which can be found in the fli4l root directory.
mkfli4l.sh
The Build Script recognizes the different boot types (Page 24).
The simplest call on Linux looks like this:
sh mkfli4l.sh
The actions of the build scripts are controlled by three mechanisms:
• Configuration variable BOOT_TYPE from config /base.txt
• Configuration file config /mkfli4l.txt
• Build-Script Parameters
The variable BOOT_TYPE (Page 24) decides which action of the Build Scripts is executed:
• Create a bootable fli4l CD-ISO-Image
• Generating the fli4l files needed for a remote update
• Generating the fli4l files and directly do a remote update via SCP
• a.s.o.
The description of the variables in the configuration file config /mkfli4l.txt can be
found in Chapter Control file mkfli4l.txt (Page 259).
5.1.1. Command line options
The last control mechanism is appending option parameters to the call of the Build Script on
the command line. The control options correspond to those in the file mkfli4l.txt. Option
parameters override the values from the control file. Out of convenience, the names of the
option parameters differ from the names of the variables from the control file. There is a long
and, to some extent, a short form:
251