* systemd has no way to set flexible enviroment variables,
though setting or dropping variables based on other settings is not
possible
* EnvironmentFile option in systemd can only have name value pairs no logic
* Best solution for this problem found at
http://www.mail-archive.com/systemd-devel@lists.freedesktop.org/msg05091.html
using a shell before starting the service
* move the parameter logic from sysvinit startup file to syslog-startup.conf
and source syslog-startup.conf from the busybox-syslog default file
* /etc/syslog-startup.conf is now the only config file
* works with bash and busybox-shell
* bump PRINC
* The Linux 3.2.X kernel has some funny issues with GCC 4.8 in the
fs/namei.c look up code. It is easier to move to 3.10 than to fully
debug the issue.
* disable the mISDN loop patch for v3.10
* use the hack to make v3.2 compilable for edison and v3.10 for dora
Use the native systemd service file to avoid running a shell script
that is ran from within the screen. This code expects the pcu to have
a .service file itself.
Provide custom systemd config files to enable the watchdog handling. For
systemd we depend on the image containing and using systemd as init script.
In case we build images without systemd we will need to install the
old watchdog. Maybe it is time to create a MACHINE_FEATURE for watchdog.
Do not attempt to start/stop the application as part of the upgrade.
This might conflict with systemd .service files that override the
LSB script. The path of systemd has changed so the path was updated
in the script. A better fix would check if the systemd cgroup is mounted
as this is a better indicator for systemd.
systemd can cope without having a dbus-daemon present. This is the
way we want it to operate to conserve a bit of memory. Do not install
the dbus daemon by default. Not having a dbus daemon is breaking the
systemd color output right now but this is something that should be fixable.
Master has moved forward and we need to move the bbappends into the
yocto-edison folder. For the task-core-boot it has been renamed to
the packagegroup-core-boot and we do not need to increase the version
number for master.
this might help us in some installations where there are multiple
back-hauls and we want to base routing decisions not only based
on the destination IP.
In the sysmoBTS 2050, we want to configure the 1PPS output of the
trimble to be active only if it has at least 1 satellite in view,
and want to make the receiver output its time information in UTC,
rather than GPS time.
sbts2050-util is a small binary-only userspace program used to
interface with the sysmoBTS 2050 board management controller,
i.e. to enable/disable PA power, read power consumption/temperature
and the like.
This tool is going to disappear once the respective features have been
included in the (open source) sysmobts-util / sysmobts-mgr. Please be
patient meanwhile.
The build differs in that it doesn't use a getty on ttyS0. In the fuutre,
a modified kernel serial driver as well as a 2050-specific utility
for managing the supervisor processor will follow.
This is a osmo-bts that will use libosmo-abis for OML and RSL and
is based on master. In one way it should improve quality in another
it is also testing.
Additional applications might store files in /etc/default and it
is the easiest to backup up all of them. This has the danger that
after an upgrade the default file is not compatible/optimal but
we will need to deal with that once it occurs.
The sysmobts-v2 version was not installed because the file was
not called properly. Rename it to gpsd-default and the sysmobts-v2
version will be picked and installed.
GPSD 3.7 is somehow exiting without us really knowing the cause. The
version 3.9 has been released and we hope that it might just fix the
issues we are experiencing.
This is a bigger update and brings the SAPI queue, readv/writev
and realtime scheduling to the sysmobts software. This will greatly
improve the stability of the software under load.
Henning Heinold
Holger Hans Peter Freyther
Holger Hans Peter Freyther
Harald Welte