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
This resolves an error message like "Can't locate bytes.pm in @INC (@INC contains: /etc/perl /usr/lib/perl/site_perl/5.14.3/ /usr/lib/perl/site_perl/5.14.3 /usr/lib/perl/vendor_perl/5.14.3/ /usr/lib/perl/vendor_perl/5.14.3 /usr/lib/perl/5.14.3/ /usr/lib/perl/5.14.3 /usr/local/lib/site_perl /usr/lib/perl/5.14.3 .) at /usr/lib/perl/vendor_perl/5.14.3//JSON/backportPP.pm line 668."
Drop the dependency and more modules. I don't feel like packaging
Types::Serialiser and then their dependencies and so on. The pure
perl based encoding does work and we don't want to run this code
every milli second.
Depend on two more modules to have the following code
my %rec_hash = ('a' => 1, 'b' => 2, 'c' => 3, 'd' => 4, 'e' => 5);
my $json = encode_json \%rec_hash;
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
Rather than parsing the existing XML or standard output of the nfacct
utility, and then piping that into a perl/python script for formatting
to JSON, we teach nfacct to generate JSON directly. This seems like
the proper way to do it. The patches will be submitted mainline.
[hfreyther: I asked henning to move forward and not test this. We
do not have dhcp/dynamic config in /etc/network/interfaces and the
link will always be up on the idu due it being connected to a switch.
ifplugd is not doing anything useful in this context]
In SYS#659 we wanted that "file" will always log to a persistent
/var/log. After I changed the /etc/default/volatiles/00_core for
the IDU and made journald persistent we still ended up having the
symlink. It appears to be caused by this script.
* When "buffer" is used we don't need to care about /var/log as
it is not being used at all.
* When "file" is set we make sure that /var/log is not a symlink.
In case of the IDU the journald should now be persistent.
For the IDU we currently want to have persistent log files. We
need to fork the volatiles script (installed as 00_core) and it
is already different between dora and current master of poky.
We are missing an sob-idu-qa check that verifies that /var/log
is not a symlink and that /etc/systemd/system/journald.conf is
set to persistent too.