Technical data

8. Documentation for Developers
configuration variables are stored for later use
(opt/etc/rc.d/rc999.template)
stored configuration variables are processed
(opt/files/usr/bin/template_show_config)
8.9. Structure of the Boot Medium
As of version 1.5 the program syslinux is used for booting. Its advantage is that a DOS-
compatible file system is available on the boot medium.
The boot medium contains the following files:
ldlinux.sys the “boot loader"’ syslinux
syslinux.cfg config file for syslinux
kernel Linux kernel
rootfs.img RootFS: programs needed for booting
opt.img Optional files: drivers and packages
rc.cfg config file containing the variables from all files in fli4l’s con-
figuration directory
BOOT.MSG Text for the syslinux boot menu
BOOT_S.MSG Text for the syslinux boot menu
BOOT_Z.MSG Text for the syslinux boot menu
hd.cfg config file to assign partitions
The script mkfli4l.sh (resp. mkfli4l.bat) at first generates the files opt.img,
syslinux.cfg and rc.cfg as well as rootfs.img. The files needed are determined by the
program mkfli4l (in the unix- resp. windows-directory). The kernel and other packages are
included in those archives. The file rc.cfg can be found as well in the Opt-archive as on the
boot medium.
12
Subsequently, the files kernel, rootfs.img, opt.img and rc.cfg together with the
syslinux-files are copied to the disk.
During boot fli4l uses the script /etc/rc to evaluate the file rc.cfg and integrate the
compressed opt.img-archive into the RootFS-RAM-Disk (depending on the installation type
the files are extracted directly into the rootfs ramdisk or integrated via symbolic links). Then
the scripts in /etc/rc.d/ are run in alphanumeric order and thus the drivers are loaded and
all services get started.
8.10. Configuration Files
Here a short list of the files generated by fli4l “on-the-fly” at boot time.
1. Provider configuration
etc/ppp/pap-secrets
etc/ppp/chap-secrets
12
The one in the Opt-archive is needed during early boot, because no boot volume is mounted at that time.
337