Technical data

2. Setup and Conﬁguration

2.2.2. Conﬁguration via a special conﬁguration ﬁle

Due to the module concept of ﬂi4l, the conﬁguration is distributed across diﬀerent ﬁles. As

editing these separate ﬁles may become tedious, it is possible to store the conﬁguration into

a single ﬁle called conﬁg directory /_ﬂi4l.txt. This ﬁle is read in addition to the other

conﬁguration ﬁles and its contents override any settings found in the other conﬁguration ﬁles.

Recall the example above: In order to conﬁgure a simple DSL router, we could simply write

the following lines into this ﬁle:

PASSWORD='3P8F3KbjYgzUc'

NET_DRV_N='1'

NET_DRV_1='pcnet32'

START_IMOND='yes'

OPT_PPPOE='yes'

PPPOE_USER='me'

PPPOE_PASS='my-passwd'

OPT_SSHD='yes'

You should avoid to mix both ﬂavours of conﬁguration.

2.2.3. Variables

You will notice that teh lines of some variables are preﬁxed with a ’#’. and thus are commented.

If this is the case a reasonable default setting is already in eﬀect. Those defaults are documented

for each variable. If you wish to set another value delete the ’#’ at the beginning of the line

and put your value between the apostrophs.

2.3. Setup ﬂavours

Previous versions of ﬂi4l only supported booting from a ﬂoppy disk which is not possible

anymore due to causes already described. There are many alternative possible nowadays,

amongst them using an USB stick.

Many other boot media (CD, HD, network, Compact-Flash, DoC, . . . ) exist and ﬂi4l may

also be installed permanently on some of them (obviously only the read-write ones). ﬂi4l may

be booted in three diﬀerent ways:

Single Image The boot loader loads the linux kernel and then ﬂi4l in a single image. After

that, ﬂi4l is able to continue the boot process without the need to access other boot

media. Examples are the boot types integrated, attached, netboot, and cd.

Split Image The boot loader loads the linux kernel and then a rudimental ﬂi4l image which

mounts the boot medium in a ﬁrst step, then loads the conﬁguration and the remaining

ﬁles from an archive residing on that mounted medium. Examples for this are the boot

types hd (Type A), ls120, attached, and cd-emul.

Installation on a Medium The boot loader loads the linux kernel and then a rudimental ﬂi4l

image which mounts an existing ﬂi4l installation without the need to extract any further

archives. An example for this is a type B hard disk installation.