* the ntpdate cron job turned into
a shell script which now checks
for running timeserver before
updating the time via ntpdate
* install the cron stanza to the
cron.d directory like serval
other packages does
* comment the entry in the old
crontab file when found
Fixes: SYS#1841
Yocto master has introduced GCC5 and this doesn't like to compile
the older linux kernels yet. This year it is time to move to a newer
LTS kernel and this can be Linux-4.1. Make space for the upgrade
by moving the recipe to a new name.
In fido the old autoload feature doesn't work anymore and we
need to remove it. Otherwise our sysmobts.service file will
create the /dev/dspl.. /dev/fpgadl... firmware upload files
and we all think that firmware loading is working.
It looks like a classic src != build dir issue of the
utility breaking the build on Yocto-Master. Try to fix
that.
ERROR: Function failed: do_install (log file is located at /home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/armv5e-poky-linux-gnueabi/rtl8169-eeprom/v0.0.1+gitAUTOINC+e62e515ce3-r0/temp/log.do_install.2455)
ERROR: Logfile of failure stored in: /home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/armv5e-poky-linux-gnueabi/rtl8169-eeprom/v0.0.1+gitAUTOINC+e62e515ce3-r0/temp/log.do_install.2455
Log data follows:
| DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']
| DEBUG: Executing shell function do_install
| install: cannot stat `/home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/armv5e-poky-linux-gnueabi/rtl8169-eeprom/v0.0.1+gitAUTOINC+e62e515ce3-r0/git/rtl8168-eeprom': No such file or directory
| WARNING: /home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/armv5e-poky-linux-gnueabi/rtl8169-eeprom/v0.0.1+gitAUTOINC+e62e515ce3-r0/temp/run.do_install.2455:1 exit 1 from
| install -m 0755 /home/builder/jenkins/workspace/Yocto-
From the obn-test config, I wrongly assumed that the inmarsat config should
be static on a vessel. Instead, we need to figure out a way to use dhcp with
linkmon.
The reverse dependency appears broken. Add a comment to
the recipes to warn us when updating. The issue does not
appear to exist in master of Yocto.
Related: SYS#1353
Barebox should be built like the kernel. We have to disable the target
userspace tools because they cannot be build using KERNEL_CC (which is
missing --sysroot=).
- remove file with wrong path to ifplugd
recipes-core/busybox/files/busybox-ifplugd.sh
DAEMON=/usr/bin/ifplugd vs. /usr/sbin/ifplugd
- use lambda expression for sysmobts/sysmobsc-kernel to
include busybox-ifplugd or not
- use different defconfig files between master
and dora to enable ifplugd or not
- use different interfaces files between master
and dora to enable auto stanza or not
for the dhcp interface
Fixes: SYS#868 and SYS#1535
[hfreyther: Try to pick an option less likely to break the
Dora support but allowing us to move forward. Not entirely
compile tested due IO load of the system]
* Disable ext2/ext3 (as ext4 can be used to mount them).
* Enable AUFS/Squshfs support
* Misc improvements (e.g. ARM optimized AES code, disable
drivers/frameworks unlikely to be used)
Jan prefers to store the fully extended .config file so we will
do it. One advantage is to more easily see what has changed between
two kernel versions.
cp ../build.sysmobts/tmp/work/sysmobts_v2-poky-linux-gnueabi/linux-sysmocom/3.10.80+gitAUTOINC+3122273386-r43/git/.config ./recipes-bsp/linux/files/sysmobts-v2/defconfig
cp ../build.sysmobts/tmp/work/sysmocom_odu-poky-linux-gnueabi/linux-sysmocom/3.2.63+gitAUTOINC+3ed283bea6-r41/git/.config ./recipes-bsp/linux/files/sysmocom-odu/defconfig
cp ../build.sysmobts/tmp/work/sysmocom_bsc-poky-linux/linux-sysmocom/3.10.80+gitAUTOINC+3122273386-r43/git/.config ./recipes-bsp/linux/files/sysmocom-bsc/defconfig
I think the last device we sold was in 2011 and I am not aware
if anyone has used it for the last couple of years. Remove it
to lower the complexity of the builds.
* add interface for connection to Inmarsat
* remove 'br0' and work directly with 'eth2' instead, to avoid bridges
in vlans of bridges
* bridge the video LAN also into the backbone (for later break-out)