Release notes
-------------

This delivery contains:
 * pcb tools package (pcbtools.tar.gz)
 * Updated Broadcom BCM963138REF SoftAtHome image (bcmwholeflash.img)
 * An example startup script (lxc.sh)

pcb tools package notes
=======================
Package was compiled with the broadcom toolchain (/opt/toolchains/crosstools-arm-gcc-4.6-linux-3.4-uclibc-0.9.32-binutils-2.21-NPTL/usr/bin/arm-unknown-linux-uclibcgnueabi-).

Updated Broadcom BCM963138REF SoftAtHome image notes
====================================================
Overview:
* Updated LXC to V1.0.7
* Manual configuration steps are no longer needed
* LXC startup hook to R/W filesystem was added to make development easier
* Really early *BETA* version of APController working with LXC is available on the build.
* Network configuration is identical to he last delivery

HowTo:
* Flash the new image using the BCM bootloader/webui.
* Trigger a reset_hard and reboot the box.
* LXC defaults can (optionally) be adapted in the boot persistent location /cfg/system/lxc/. It might be needed to remove some cgroup limitations in the default settings.
* LXC defaults point to /cfg/system/root as location for the LXC containers.
* You can create/launch containers manually using lxc-create/lxc-start.
* Optionally add a hook in the R/W (boot persistent) filesystem to setup your container/rootfs so that your board and container are configured automatically at boot time.
  Do this by adding a script called /cfg/system/lxc.sh and make sure it is executable using chmod +x. An example lxc.sh can be found in attachment, but you can customize this script in any way you want e.g. mount from usb etc.)
* If you want to use the APController to manage (start/stop) your container, use "ap" as containername. If an "ap" container is available, it will be automatically started at boot. All other container names are not managed by APController.
* Some tests were made with a container containing the pcb tools and dbus bridge. Everything seemed to work properly. The pcb bus interconnection was created manually by listening on the AP ("pcb_cli Bus.listen("pcb://0.0.0.0:9999",true)") and connecting from the NP ("pcb_cli Bus.interconnect("pcb://10.129.0.2:9999",true,true)")

Limitations:
* lxc-checkconfig does not work on the board as we do not have zgrep (GPLV3) on board. You can copy the board's /proc/config.gz to your pc and run he tool installed on your pc
* lxc-clone does not work
* Kernel is still 3.4, so there still are some limitations for lxc
* The verion of APController is a really urly BETA, so it is very likely that there will still be issues.
* Network configuration for management channel between NP and AP still needs to be fixed
* AP WAN routing will only work with ethernet uplink
