packages.

The file zz~-ffpb-upgrade will only be delete if its return value is 0.
For some reason we forgot to add an 'exit 0' at the end of the file if
everything is OK. This has been added.

To deal with invariant scripts that were not executed properly, we now
test the return value of do_component for these scripts as well. The
function do_component however may return early with a return code not
equal to 0, if a version for that package/script could not have been
determined. We now return the code 255 in this case and ignore that
state in "main", as we are not interested in non-ffpb packages.

The package by now was rather aimed to target on the migration of
TP-Link TL-WR1043NDv2 devices from a pseudo-stable firmware to the
officially stable version 0.6.0.

However, as it might become necessary to change other configuration
values from AA to be compliant with their corresponding values in BB
independent from the particular hardware-type, the package got renamed
to reflect this use. Moreover, as there only is the need to migrate
TP-Link TL-WR1043NDv2 devices once, with the new name the package can be
reused for the migration to Chaos Calmer by adapting the included
scripts.

Closes issue #2 by adding appropriate tests to the script as requested
by @hej, such that values that have already been set to a higher value
to not get changed.

As its name states, this packages applies some config optimizations
(like tweaking kernal knobs via sysctl) on the nodes.
For the most knobs Gluon sticks for OpenWRT defaults for good reasons,
as some values need to be set according to the environment of the
nodes (e.g. the network's size). As OpenWRT basically aims at provid-
ing a stable system for standalone WiFi access-points, the system's
default configuration may not be appropriate anymore the larger the
network grows, though.

By now, the package was trying to overwrite "/etc/banner" in the image,
which caused opkg to stop the operation, as this file is already
provided by the base-files package. Without the --force-overwrite option
set for opkg (e.g. in the global gluon Makefile, where it is not set by
default), the installation of the package will fail.
Hence the problem got circumvented by renaming the customized banner file
provided by this package to "/etc/banner.ffpb" and using the prerm,
preinst, and postinst hooks of the packages' make-file to rename the
already existent "/etc/banner" to "/etc/banner.openwrt" and establish a
symbolic link "/etc/banner" to "/etc/banner.ffpb".
For deinstallation of the package, this link gets removed and a new one
(pointing at "/etc/banner.openwrt") gets created.

Using these macros (instead of $(CP)) in the Package/.../install section
ensures correct permissions of the files installed in the image. The script
ffpb-alfred-watchdog itself now get installed to /bin using INSTALL_BIN,
while the corresponding cron-file gets installed using INSTALL_DATA. In both
cases we ensure that the directories exist by calling INSTALL_DIR (with
parameters "/bin" and "/lib/gluon/cron" respectively) prior to installing
the files.

DATA, BIN} macros.

Using these macros (instead of $(CP)) in the Package/.../install section
ensures correct permissions of the files installed in the image.
The two scripts ffpb-debug and ffpb-debug now get installed using
INSTALL_BIN, while the (orphaned) cron-file gets installed using
INSTALL_DATA. In both cases we ensure that the directories exist by
calling INSTALL_DIR (with parameters "/bin" and "/lib/gluon/cron"
respectively) prior to installing the files.

ffpb-debug-report on crash.

As it is only assumed that the bug, which causes A.L.F.R.E.D. 2013.4 to
crash, got fixed in 2014.1, it is important to know whether or not this
really is the case. Hence, an additional check got implemented that
tests for the A.L.F.R.E.D. daemon's major version. If the major version
is greater than 2013 an additional ffpb-debug-report gets issued
automatically, so that the dev-team gets informed about the crash.

Monitors whether or not the A.L.F.R.E.D. is still running on a node or
not. Version 2013.x crashes from time to time and thus some nodes dis-
appear from the map. It is thus suitable to monitor the state of the
daemon on the node itself by periodically making requests to avoid un-
necessary support-requests and manual restarts of these nodes. In a
failure state, the daemon can simply be restarted by triggering its
init-script.

Please note that the bug is most likely gone in v2014.1 and newer and
and thus the package does not need to be included in the firmware in
newer firmwares.

First of all, the ffpb-debug script is now written in lua and thus requires
a lua interpreter to be installed. But since the script makes use of some
gluon-specific lua-functions/-variables (such 'site_conf' in site_conf.lua),
we have to make ffpb-debug depend on the 'gluon-core', which in turn would
define all other dependencies.
Moreover, since ffpb-debug-live got rewritten to work with Barrier Breaker
(i.e. gluon 2014.4 and later), the already defined dependency towards the
busybox package does not suffice any longer, as we fetch interface-details
and -statistics via ubus now. As ubus outputs its data in JSON, we moreover
need the helper functions from the 'libubox' package for a convenient hand-
ling of such data in shell scripts.

It was only used in a local test and the same functionality can
be accomplished in the next Gluon version by setting
`siteconfig.authorized_keys`.

Wifi Blackout Workaround (Extension of ffpb-debug)

This patch extends ffpb-debug to include additional WiFi infos and values from the ath9k-debugfs (as proposed in gluon issue #130).

Due to the WiFi blackout problem with ath9k devices, gluon devs request additional
debugging data from the ath9k debugfs [1]. We follow this advice and try to fetch even
more data from the debugfs for ffpb-debug.

[1] https://github.com/freifunk-gluon/gluon/issues/130