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.
Creating a new file in /etc/sysmocom/backup.d/ that ends with .backup
will be read during the backup and then be restored. This way we can
easily extend the files to backup.
* 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
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
* setting APPEND in the image file overwrites
the APPEND from boot-directdisk.bbclass in edison, which
creates the syslinux.cfg without "root=" stanza
* for dora we do not use syslinux or the image-directdisk
so revert this paticular changes
Fixes: SYS#373
If we don't provide a DNS server via DHCP to the BTSs, then their
ntpdate will not succeed in contacting pool.ntp.org (resolver failure),
which in turn means they have the wrong date, which again in turn leads
to failing opkg update or openvpn certificate verification failures.
* use seperate defconfig, because of option changed from 2.6.39 to 3.10
* use python magic to switch between linux and linux-sysmocom
* add sysmocom-bsc to compatible machines for linux-sysmocom
* add new confiugration parameters for syslinux
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.
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.
We have some images that need the real wget for upgrades, the SSL
root certificate of CA-Cert but that doesn't use task-sysmocom to
build the image. Move these utilities into the tools task.
This sanity check is included in the used bbclass directly and to
support both Edison and master we will need to remove the custom
python code due a change in indention in the python code.
We should use perf for future performance problems but it might
require more work (e.g. not to install the source into the -dbg
package, adding newt, etc.). But oprofile is not very nice to
use right now anyway.
This sadly still prints the firmware reload messages. But this is
necessary right now. The fpgadl/dspdl drivers do not log fatal
failures so the 'success' is the only information we have. This
is to be fixed in the driver.
If the first partition of a MMC card is mounted and has a logs/
directory syslog will start to write log messages to the MMC card
in the directory /media/mmcblk0p1.
This issue is documented in PRJ#72. The easiest is to to keep the
old software running as everything else is racy and start-stop-daemon
does not appear to implement the --retry command. Let's see how
far we get with this workaround.
We want to only log a given loglevel, backport the start up script
from OE-Core to get the LOGLEVEL variable. This removes the MARKINT
and adds DROPDUPLICATES and LOGLEVEL.
The modules depend on kernel-base (renamed kernel-3.2.35) package,
the tasks depend on some modules and nothing needed the kernel package.
In OE Core/Poky the machines depend on kernel-modules which will pull
the kernel package into the rootfs. We do it by hand using the essential
depends and bumping the PR for the task-core-boot.
I have verified that on a kernel ugrade task-core-boot will be updated
and the kernel package is installed.
The idea is that the basic extension resides inside the the normal
recipe directories. Depending on the version of poky the bbappends
need to be included. Appends applying to all versions will be put
into the shared folder, specific ones into the specific directory.
Once a bbappend can not be shared anymore it needs to be copied.
Holger Hans Peter Freyther
Jan Luebbe
Henning Heinold
Harald Welte
Holger Hans Peter Freyther