This change adds an initramfs module to mount the data partition and
restore the backup to the overlay. It is enabled by adding it to the
image-rauc-slot-initramfs recipe.
Signed-off-by: Jan Luebbe <jluebbe@debian.org>
The new version searches mounted slots for matching files referenced by
the new manifest. This avoids downloading files we already have on the
system.
Additionally, the new version includes better error handling and more
unit tests.
Signed-off-by: Jan Luebbe <jluebbe@debian.org>
Splitt of the actual rescue root filesystem to
image-rauc-rescue-initramfs and build image-rauc-ubi using
kernel+initramfs (like normal rauc slots).
Signed-off-by: Jan Luebbe <jluebbe@debian.org>
The NTPd/GPSd SHM interface does not seem to work. Instead use the
native GPSd refclock (46) and configure it with the measured offset.
Signed-off-by: Jan Luebbe <jluebbe@debian.org>
The configuration scripts are named for the systemd units for which they
generate configuration files. The generator causes them to run before
those units are started.
If /slot/system.conf is missing, we just exit the generator.
This reboots the system instead of starting a shell on boot problems.
Because the slot will only be marked as sucessfully booted as the last
step in a normal boot, repeated emergency boots will cause a fallback at
the boot chooser level to the other slot.
Testing this is possible by passing 'emergency' via the kernel command
line.
Hopefully, this installs a different /etc/default/udhcpc file on
sysmocom-idu machines. Not sure if adding a machine subdir suffices.
The idea is that the machine-specific subdir symocom-idu should replace
the udhcpc.default file used for the idu packages, only, which has both
resolv.conf mods and default route disabled by default.
The IDU requires that udhcpc does neither touch resolv.conf nor install a
default route. Add a flag to switch off default route installation, the
resolv.conf part is already switch-off-able.
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 builds of the stable upgrade and the Yocto-Master failed
because of the commit gone missing (no remote is referencing
it). I created a dummy branch to hold this commit.
* We never need the BTS firmware. We never want to do GSM from
within rescue image
* Remove various udev hardware dbs. I think we couldn't care less
about identifying peripheral devices by name and such.
The system should be as small as possible and besides tools to
touch flash and block files, SSHD and rauc there should be nothing
else. We might continue to have opkg on it to allow updating it
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