Technical data

3. Base conﬁguration

hd Choose this to boot from a hard disk. You will ﬁnd more information in the Docu-

mentation (Page 118) of the HD package.

cd Choose this to boot from CD-ROM. With this setting, the ISO image ﬂi4l.iso will be

created which you have to burn onto CD with your favourite CD burning application.

Please pay attention to choosing the right driver for your CD drive.

integrated Choose this if you do not plan to use a conventional boot medium but e.g.

want to boot over a network. This setting integrates the OPT archive into the

RootFS so the kernel can extract everything at once and does not need not mount

a boot medium.

Note: You cannot perform a remote update of your ﬂi4l router in this case.

attached This setting is similar to integrated but it does not integrate the contents of

the OPT archive into the RootFS; rather, the OPT archive is put “as is” into the

/boot directory. From there it will be extracted during the boot process.

Apart from that, the caveats described for integrated apply to this boot type as

well.

netboot This setting corresponds to integrated. However, the script mknetboot.sh

is additionally run to create an image for booting over the local network. Please

read the wiki https://ssl.nettworks.org/wiki/display/f/fli4l+und+Netzboot for

further information.

pxeboot Two images are generated, kernel and rootfs.img. These are the two ﬁles to be

loaded by the PXE bootloader. During execution the local tftp directory may be

speciﬁed and in addition a subdirectory in the tftp directory (–pxesubdir). Refer

to the Wiki here as well: https://ssl.nettworks.org/wiki/display/f/fli4l+und+

Netzboot.

Note: How to conﬁgure ﬂi4l as a boot-server (pxe/tftp) you can ﬁnd in the documenta-

tion of opt dns_dhcp!

LIBATA_DMA Default Setting: LIBATA_DMA=’disabled’

This options selects if DMA is used for libata based Devices. It is needed for example

for incompletely wired IDE to CompactFlash Adapters. Select ’enabled’ to use DMA.

MOUNT_BOOT Default Setting: MOUNT_BOOT=’rw’

This variable speciﬁes how to mount the boot medium. There are three possibilities:

rw – Read/Write – Writing and reading is possible

ro – Read-Only – Only reading is possible

no – None – Medium will be unmounted after booting and can then be removed if

desired

Some conﬁgurations require mounting the boot medium read/write, e.g. if you want to

run a DHCP server or if you want the imond log ﬁle to be stored on the boot medium.

BOOTMENU_TIME Default setting: BOOTMENU_TIME=’20’