Specifications
with an ext2 file system and contain the label "SuSE-FWFloppy". Without this
label, the configuration floppy is not recognized. The FAS (Firewall Adminis-
tration System) on the Adminhost creates the file system and the label auto-
matically. The configuration floppy is loaded while the Live CD is booted.
Creating the Configuration Disk
The configuration floppy disk can be created on the Adminhost with FAS.
Under ‘Configuration’, select ‘Create floppy disk’. Editing the configura-
tion files with an editor should be left to experts. If necessary, use the edi-
tor module of FAS or first create a configuration floppy disk with FAS then
modify this according to your needs. There is no support for this.
The Configuration Files
The following overview of the configuration files located on the disk is for
information purposes only. The files are generated by the Admin desktop:
/etc/hosts See the man page for hosts (man hosts)
/etc/hosts.allow See man 5 hosts_access
/etc/hosts.deny See man 5 hosts_access
/etc/inittab See man inittab
/etc/isdn/ Contains the configuration file for ISDN isdn.conf
/etc/cipe/ Contains the scripts ip-down and ip-up
/etc/live-setup.conf Preparing the hard disk
If you set hSETUP_DISK=yesi, the hard disk is repartitioned every time
the system is booted without asking for confirmation. This means that
any existing data is lost. The first partition (/dev/hda1) is used for
swap and the second partition (/dev/hda2) for /var.
/etc/ppp/ Directory for ppp configuration
/etc/modules.boot In the file /etc/modules.boot, specify loadable ker-
nel modules to loaded when the system boots. It is not necessary
to specify paths relative to /lib/modules/<kernelversion>/.
Modules can be given with their names (without a .o file exten-
sion), for example, tulip <options> or, with the absolute path,
/opt/mymodules/tulip.o.
126 The Configuration Disk










