* take the baudrate for the grub serial console setting
from the kernel-cmdline which the system was booted from
* better parsing of the options which the install-script
gets from init
* Video Mode, VGA mode are not used right now and make it
empty right now.
* when restoring links e.g. for systemd files
the links will be created with content// prefix
* use transform instead of strip to remove
the "content/" prefix
* bump PR
Add post install script that will mangle the config to be the
right one for the given machine. This will be executed once
after the post installation. In case of the getty change the
system must re-start once to be fully usable. E.g. for the
sysmoBTS2050 the PA might not be powered up on first boot.
The sysmobts-2050 machine does inherit from the generic bts so
we do not need an exact copy of the configuration file.
The watchdog is not used in dora or later images as this functionality
is integrated into the systemd.
Related: SYS#559
We want to have a single image that will do the right thing on
the various BTS models we have. This means we will install the
sbts2050 utilitiy (it clashes with sysmobts-mgr anyway) and the
gpsd with a default config for it.
The sysmobts-v2 config file was for a specific usecase and is
obsolete for all intents and purposes. Make it the default
Related: SYS#559
We need to replicate the other services that were included with
*.service. Install an additional alignment.service that is required
for ARM. The actual service file is from Daniel and copied from
the postinst and sysmobts service.
I wish I could have made it more simple but at least only compare
the 1.X of the poky version as minor versions generally do not
upgrade the core components
Having:
osmo-bts requires sysmobts-firmware > 3.11
sysmobts-firmware requires osmo-bts > 0.4.2
is something opkg can't resolve in one go. One needs two calls to
the opkg command to end up with a fully upgraded version. Make sure
that we require/pull newer firmware when installing a new version
of osmo-bts.
* Add sysmobts-firmware 3.11. The firmware will work with the
previous osmo-bts software and this one (as we don't use the
new primitives)
* Build newer version of osmo-bts with support for online
calibration and CMR fixes.
Enabling the "systemd" feature will enable the socket activation
feature used by systemd. This way we can (re-)start the GPSD based
on the socket activation.
If the year is smaller than < 2014 an initial date will be set. This
has been manually verified by copying ntpdate to ntpdate.off and making
sure that the VPN is coming up. Due the short SSL lifetime of CACert
we will need to update the script once in a while. But our VPN should
now always come up.
The TI Davinci DM644x and the TI Sierra AM335x both feature a
watchdog. Enable it on the AM335x as well. The next part is that
we can enable the watchdog for the shutdown. E.g. in case the
system does not reboot after the shutdown.
The shutdown is executed last and only after the shutdown target
has been reached. For time timeout we need to use the same interval
as the watchdog (as both drivers don't allow to change the timeout
interval).
Henning got really confused that the "a.b.c:1234" he passed to
gps2udp showed up as "a.b.c 1234" in the kernel cmdline. Use
strdup to take a copy of it.
Fixes: SYS#424
systemd doesn't look in /etc/rcS.d for init scripts so we never
start networking unless we are using ifplugd. We need to check
how this behves on the sysmobts and sysmobsc in case the network
is being started twice.
Daniel Willmann
Holger Hans Peter Freyther
Henning Heinold
Harald Welte