When restoring the backup the rootfs is mounted in /rootfs/data
and the symlink to the real file would then not work. Attempt to
change the directory first to get a relative symlink.
Untested change and needed for rauc
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.
* use printf instead of echo
* add missing /etc/ for the udhcpc-default file
* add log-entries for all shell actions in the
post image setup
* generate comments in all files which are touched
Related: SYS#1774
We can not have sysmocom-backup-default and sysmocom-backup-data-default
installed at the same time. I don't want to play games with RREPLACE and
RPROVIDES either. So simply use one of the two files. Copy the two more
default values over to the other recipe.
Create a sysmocom-nitb-rauc-image and create a rauc packagegroup
with the default depdencies and an include file to be used by
other images. This assumes that sysmocom-image.inc has been
included first.
With the ro image we have a cheap way to figure out which
files were changed. We can run cmp between the to be backed
up file. This way the stored data will be minimal in the
sense of changed files.
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.
When using squashfs + overlayfs a root, we need to store the backup
somewhere else and restore it on every boot. Do avoid breaking existing
users, this is implemented in a separate recipe (as suggested by Holger).
Move the default file list to a separate file in /etc/sysmocom/backup.d,
which is itself included in the backup. Also create a symlink to the
most recent backup.
The /boot directory is excluded from the squashfs image only, as in that
case it is stored separately. This allows booting normal sysmocom images
as rauc slots.
Add the new task to task-sysmocom-feed so it is being built by
default in our CI infrastructure.
make iputils available as well for people wanting to use a real
ping/traceroute/arping.
Related: SYS#1190
The notion of "task" has been deprecated for a long time because
the word is used for different things. The new word is "packagegroup"
which describes the usage of "task-*" in a more obvious way. Dora
and master builds can fully use packagegroup-* for everything and
for edison we would need to spend some time to add a provides for
packagegroup-* to the task- group. I don't intend to work on the
edison part right now.
* the entry "option subnet" takes the
subnet mask not the subnet address,
while the busybox dhcp-client was
fine with it, the isc-dhcp-client complained with
Error: an inet prefix is expected rather than "10.23.24.113/10.23.24.0".
The concept of directdisk image is overhauled as we are now
having a initramfs that can flash the next image through USB.
The dedicated E1/IP images are rarely to never used and did
probably bit-rot. For the next time we provide such a system
we can simply (write a script to) install the additional feed.
Harald Welte
Holger Hans Peter Freyther
Jan Luebbe
Henning Heinold