Kown bugs and available patches in fli4l 2.1.12

   The fli4l team

Fixed bugs
##########

The following bugs have been found and a fix is provided in the archive
[http://www.fli4l.de/german/extern/bugs/fli4l-2.1.12-patch-1.tar.gz - fli4l-2.1.12-patch-1.tar.gz] 
Simply extract it like any other OPT. You can also have a look at the
[http://www.fli4l.de/german/extern/bugs/fli4l-2.1.12-patch-1.diff.html - diff]
or [http://www.fli4l.de/german/extern/bugs/fli4l-2.1.12-patch-1.diff - download] it.

The patch is updated if new problems are found. It always has to be extracted as the very last archive.
The latest patch always contains all the fixes of the preceding ones. 
Latest patch: PATCH_DATE, PATCH_SIZE Bytes

Patch 1
=======

:ISDN-Circuit-Setup:
  A warning could occur because of a not correctly initialised variable;
  this caused no further problems.

:DMZ-Setup:
  Because of an error in the way the packet-filter-rules were created,
  services provided from within the DMZ could not no longer be reached.

:mini-httpd syslog display:
  The number of lines was not output when viewing the syslog file.

:hd-install:
  Even though fli4l now support LFS, this feature was not taken into
  consideration when partitioning the HDD. After applying this patch you
  may create partitions larger than 2GB.

:dns:
  An error has been fixed that occurred during the creation of the
  file /etc/host.

:text menu:
  Several spelling mistakes have been fixed.

:windows-build:
  Two errors were fixed that occurred when creating the fli4l files on a
  network share or within a path that contains spaces.
  Because of these errors, files did not have the correct permissions
  specified in opt/<packagename>.txt, but were created with the default
  value of 0555. This could lead to problems, such as the the lpr-daemon
  from the package samba_lpr no longer being able to process files due
  to insufficient permissions.
  When using ssh-keys to transfer files via scp an error occurred due to
  a wrong variable name. This has also been fixed.

Known problems
##############

We aren't aware of any other problems with this version, yet.