Restore "openvpn@.service" from packaging of openvpn 2.3.6, so we can
start the sysmocom vpn the same way as currently described in the
manuals.
Previous patch 8439e71a99 already
attempted to do this, but only brought back "openvpn.service" and not
"openvpn@.service".
Fixes: 8439e71a ("openvpn: bring back openvpn.service file")
Related: SYS#6303
Change-Id: I28a7f491d74690409f815555743679c69e31b518
Import current packaging of dropbear from openembedded-core.git, commit
0defbb5925e309799162e221285e4cfb2e2c2ca5.
Related: SYS#6402
Change-Id: I431934b0558350931bb9571b0fa6efff8ba45387
Remove this directory to prepare to upgrade dropbear in following
patches. The directory made changes to the sysvinit script that was
used by pre-201705 systems (SYS#691). 201705 uses systemd services
instead.
On a side note, all customizations made to the init script had been
upstreamed into OE.
Related: SYS#6402
Change-Id: Icb65a68091aff43c5c94ba961a650865a2784b65
Package OpenSSH's sftp-server program, so we can install it as
dependency of dropbear in a future patch. Once sftp-server is installed,
the scp tool from OpenSSH can be used with the SFTP protocol, without
enabling the legacy flag for the legacy SCP protocol.
The sftp-server binary is 126K in size.
After packaging this, I realized that we could also have used
the openssh-sftp-server package from poky:
https://gitea.sysmocom.de/sysmo-bts/generic-poky/src/branch/pyro/meta/recipes-connectivity/openssh
But let's use this extra package now, it uses the most recent OpenSSH
source and doesn't build the rest of OpenSSH which we don't need.
Related: SYS#6403
Change-Id: I376bc31413935f7a560afd916a623228550dc6fe
Adjust the bundled udev rules to use gpsd.hotplug instead of
gpsd.hotplug.wrapper, as the wrapper has been removed upstream.
Fix for:
systemd-udevd[1004]: failed to execute '/lib/udev/gpsd.hotplug.wrapper' '/lib/udev/gpsd.hotplug.wrapper': No such file or directory
Fixes: 6a8f914b ("gpsd: upgrade to 3.24")
Related: 711a3f8412
Related: SYS#6222
Change-Id: I95c9d1537a9a7090b1239aecef14f25f8d7ca554
Restore the openvpn.service file from packaging of openvpn 2.3.6, so we
can still start it the same way (as currently described in manuals).
Related: SYS#6303
Change-Id: I2cf96bc1ecca79ae98be1181fbd3c15edad15ca8
Our openvpn server has meanwhile been migrated to 2.5.x, and
establishing backwards compatibility with 2.3.x means we have to
disable ciphers + tls versions that are no longer considered secure.
Related: SYS#6303
Upgrade gpsdate to the latest commit, where the build against newer gpsd
was fixed.
Related: SYS#6222
Change-Id: Ia83008933a1e94e556b6908903ad7b63759fc1e3
Usually when upgrading packages, we just copy the upstream package and
adjust it slightly. I've looked at the upstream package here:
https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-navigation/gpsd
(HEAD at f3d14d41ad60d2d52a0ea795ae10fe0882146ed1)
But as I compared both packaging trees, I found ours is quite different
than upstream. We have a lot of additional patches, still use python2 and
have these extra files:
├── gpsd
│ ├── 60-gpsd.rules
│ ├── gpsd
│ ├── gpsd-default
│ ├── gpsd.service
│ ├── oc2g
│ │ ├── gpsd-default
│ │ └── gpsd.service
│ ├── sysmobts2100
│ │ └── gpsd-default
│ ├── sysmobts-v2
│ │ └── gpsd-default
│ └── sysmocom-idu
│ └── gpsd-default
Therefore I didn't start with the upstream packaging but instead
increased the gpsd version in our packaging and went through each patch
to see if it can be dropped or needs to be forward ported.
Change the version by renaming the .bb file. Reset the version of the
recipe (PR) back to "r0" again, as it is common practice after changing
the package version. The previous value "r3.20" looked a bit like a
package version, but it's not that.
Rebase patches:
* 0001-gps2udp-Add-a-label-timestamp-and-mac-address-to-eac.patch
* 0002-gps2udp-leave-argv-untouched.patch (leave-argv-untouched.patch)
* 0003-tsip-configure-and-enable-1PPS.patch (gpsd-tsip-pps.patch)
Add build fixes:
* 0004-SConscript-force-use-of-pthread.patch
Drop patches:
* 0001-SConstruct-prefix-includepy-with-sysroot-and-drop-sy.patch:
unused in previous version
* 0001-SConstruct-disable-html-and-man-docs-building-becaus.patch:
doesn't apply, instead disable docs building via manbuild='no'
* 0002-SConstruct-respect-sysroot-also-in-SPLINTOPTS.patch:
not needed anymore (no splintopts line in 3.24)
* gpsd-3.3-ldflags.patch:
fixed upstream
* no-rpath-please.patch:
doesn't apply, not needed anymore (see 5df2de36 in gpsd.git)
Related: https://docs.yoctoproject.org/bitbake/2.2/bitbake-user-manual/bitbake-user-manual-ref-variables.html#term-PR
Related: SYS#6222
Change-Id: I2debe481c5f1cc4ee8290ad0dc883d6a4ea73741
Build osmo-bts and osmo-pcu from the tag instead of the commit, so we
don't need to update the commit. This is how it works in
meta-telephony.git already.
Fixes: 9a554791 ("Update Osmocom recipes to latest tags (release 202302)")
Change-Id: Id55552c25dc49fee6d6b48f2b5c50b008104ba60
Package sysmocom-openvpn-config was recently added to
task-sysmocom-tools. That task is pulled in by default into images. We
don't actually want that. Instead, we want the package to be available
in feeds, but without being installed into the image by default. Hence,
revert the recent commit and put the package in task-sysmocom-feed.bb
instead.
Fixes: d8cb7e21d0
Related: SYS#5734
This reverts commit 34d053fbe8.
It was found that this patch (from 7 years ago) breaks upgrade path and
current behavior (user manual) of the sysmocom VPN.
It is expected that the systemd service openvpn.service is disabled by
default, and that the user simply has to enable/disable it to
enable/disable the sysmocom VPN.
This affects all images deployed until today, since until recently an
old sysmocom-openvpn-config package (from around 2013) was being used
during provisioning, instead of using the one we recently made available
into the regular 201705 feeds.
Related: SYS#5734
Fix sysmocom-openvpn-config not getting built by adding it to
task-sysmocom-tools.
Related: SYS#5734
Change-Id: I918f1ef9170f4beefb6ac07ad08678c208476559
Do not try to use "mktemp --tmpdir" in the update-ca-certificates
script. This broke upgrading, as the script gets executed during
post-upgrade.
Related: 66951d3b45
Related: SYS#5283
Current list is missing osmo-sip-connector.cfg. Let's just include the
whole directory.
Fixes: SYS#5632
Change-Id: Ia2376aaa8c5aae90ce00a86fe616a913ecaf025d
They are not maintained nor used anymore.
* osmo-bsc-sccplite: Use osmo-bsc from osmo-bsc.git instead.
* osmo-nitb: Use osmo-msc from osmo-msc.git instead.
Related: SYS#5247
sysmocom-alix and sysmocom-apu2 are both based on sysmocom-bsc
Since we use those for the 3G starterkits add iu distro feature which
will install osmo-hnbgw and build osmo-msc and osmo-sgsn with iu
support.
osmo-pcap recipe has been recently added to meta-telephony 201705, so
let's make sure it's available in feeds (and at the same time make sure
it builds fine over time).
Depends: meta-telephony.git I5bb85b118029d1559a958803184690a9d0f23e4a
The filesystems are now mounted in the same way the sysmobts2100
build does it.
This fixes the failing checkflash systemd service on the oc2g.
Related: SYS#4493
This is needed for osmo-bts to properly transmit on OC2g because it
contains calibration values for the amplifier. Without the transmit
power will be really low (probably just what leaks through the amp).
The autobauding feature of gpsd would not work even once the correct port was
set. The systemd service file now sets the baudrate of 115200 before starting
gpsd.
I got th following error while building meta-sysmocom-bsp in my
ArchLinux setup, probably due to using a newer git version.
ExpansionError: Failure expanding variable REPOGITFN,
expression was ${@get_repo_gitfn(d, '.../system-images/git/meta-sysmocom-bsp/recipes-support/lc15-sysdev-remap/files', '')
REPOGITFN is expanded using function get_repo_gitfn in
gitver-repo.bbclass, which ends up calling:
git -C .../system-images/git/meta-sysmocom-bsp/recipes-support/lc15-sysdev-remap/files rev-list --count HEAD ''
fatal: empty string is not a valid pathspec. please use . instead if you meant to match all paths
It's not actually being built by any job, and its contents are anyway
wrong since it basically pulls in the same as the sysmocom-nitb-image.
Initially it made sense to have these 2 images because we either
connected the BTS to osmo-bsc or osmo-nitb. This is no longer the case
since we deprecated osmo-nitb, and now it always connects to osmo-bsc.
The initiall idea after osmo-nitb split was to have a sysmo-bsc-image
containing only osmo-bsc, and then a sysmocom-nitb-image superseeding
it by installing all other core network components such as hlr, msc, etc.
Since there's no real need for that now, and in any case we can just
duse the nitb one and disable the extra services, let's drop the bsc
one.
This way we have it too in sysmocom-nitb-image, but only when needed,
that is: when we build for a machine inheritinh from sysmocom-bsc, which
is a machine not containing any BTS HW and thus requires a BTS connected
to it, so it needs a DNS server to serve it.
According to MACHINEOVERRIDES, alix and apu2 are subclass machines of
sysmocom-bsc (abstract superclass). However, only alix requires
sysmocom-bsc.conf. Make both alix and apu2 requires sysmocom-bsc.conf,
and move alix specific stuff to sysmocom-alix.conf.
In the process, linux-firmware-rtl-nic is removed from RDEPENDS for
apu2, since it doesn't use RTL nic but e100e/igb ones.
As a result of these movements, osmo-bsc.conf is actually empty, but
it's left there for future additions which have to affect both machines:
ie. adding stuff which is expected for "bsc" role on machines containing
no BTS.
After upgrading to poky pyro, generation of grub2 menuentry in grub2
became broken. Our init-install.sh script, origianlly coming from an old
poky version, was modified in poky
c2e63957d5abaa4bb10507da5ba16f01112d0bf5 to adapt to the fact that
/etc/grub.d/40_custom was not there anymore. We need to do the same,
otherwise the menyentry is not appended to the grub config and the
installed image won't boot correctly.
poky script ./meta/recipes-core/udev/udev-extraconf/mount.sh is called
by systemd-udev rules every time a storage device is found, and it is
responisble to automount them. The init script waits until the device is
automounted to finish the boot process.
The mount.sh script sues "stat", and right now our busybox doesn't have
it enabled. As a result, stat is not found, the script fails, the
device is not mounted, and the init script hangs forever.
Since osmo-msc a2353c69cc3d2ccc7caee4571b3b8d2a98961150 and
osmo-bsc 3561bd48976dbee8dbd4659dad15be85a3e79ace osmo-bsc-mgcp support
is dropped in favour of osmo-mgw and one instance of osmo-mgw can be
shared between osmo-msc and osmo-bsc.
This patch is not longer used since the complete declaration of the
function was removed from the header file in osmo-bts
085569df55ceb3737b79f53b015b0c064698ddc6.
osmo-mgw recipe in meta-telephony has been updated to generate several
packages. Right now, osmo-bsc requires osmo-mgw service, but osmo-msc
still requires osmo-bsc-mgcp, so let's add both to the image.
After switch to linux 4.9.14, make oldconfig run by OE was disabling
CONFIG_IP_NF_TARGET_MASQUERADE even if original defconfig had it enabled
as a module. This target is required for osmo-ggsn.
This new package group contains what used to be the "task-sysmocom"
group, with an osmo-nitb. In turn, task-sysmocom.bb will be changed to
use new git repositories.
According to documentation, they are deprecated by
KERNEL_MODULE_AUTOLOAD:
WARNING: linux-sysmocom-4.9.14+gitAUTOINC+8d5d275254-r1 do_package: module_autoload_leds-gpio was replaced by KERNEL_MODULE_AUTOLOAD for cases where basename == module name, please drop it
After switch to linux 4.9.14, make oldconfig run by OE was disabling
CONFIG_IP_NF_TARGET_MASQUERADE even if original defconfig had it enabled
as a module. This target is required for osmo-ggsn.
WARNING: osmo-pcu-0.4+gitAUTOINC+0cd8e4eade-r5.18 do_configure: QA Issue: osmo-pcu: configure was passed unrecognised options: --enable-sysmocom-bts [unknown-configure-option]
Looking at ./configure --help in osmo-pcu, that option doesn't seem to
be available. The recipe is already using --enable-sysmocom-dsp too,
which is correct.
Commit d32cbbb13087eae2617920d4ea980f0e8869a89e changed --enable-sysmocom-bts to --enable-osmo-bts.
Later on, commit 08e5d604d3fce75b955549244b36fde62f20894b removed --enable-osmo-bts option.
In the past I copy and pasted the compiler-gcc4.h to have gcc-5.h and
gcc-6.h suffix. I didn't want to do the same for gcc7 and cherry picked
the original commit. Not compile tested though.
Current u-boot version cannot handle correctly ext4 formated with 64bit
option, which is enabled by default with recent versions of mkfs.ext4.
If option 64bit is enabled, u-boot reads the filesystem erroneously,
listing wrong directories or displaying some directories such as /boot
as empty, which forbids itself from loading the kernel and failing to
boot.
See #3733 and https://github.com/armbian/build/issues/279 for more
details.
Modules in lib/ net/ and mtd/ are ignored as they do not seem to be
relevant. Previous patch did not include it due to interdependency
problems between kernel modules which are not resolved
automatically. This is fixed now.
* use systemd class to auto-enable installed services
* make sure lc15-sysdev-remap is started before lc15bts-mgr
* keep BTS-specific name to enable adjustment via service file template
in future versions
Rename:
sysmobts -> osmo-bts-sysmo (available in master since 114293a414bd5b7c86622ec8c293c4034c80d243)
sysmopcu -> osmo-pcu (available in master since 241f5bcb00f9c6fee4200a3aea9aa497bf0d3eee)
Old names are still available via alias.
Note: the script is imported as-is, but .bb file is modified because we
use .service file from previous patch instead of init file. I'm not
familiar enough with bitbake to be sure that the changes are correct so
I'd appreciate thorough review.
Move the shared files into yocto-fixes/ and the files from master. The
next step is maybe to remove the indirection again. We will see about
it in the future.
We have machine-specific systemd.conf for sysmobts2100 and owhw, but we
didn't add them to SRC_URI so far, resulting in them not being used as
intended.
We need to makes sure that the dsp/fpga related kernel modules are
included in any image we generate. Use MACHINE_ESSENTIAL_EXTRA_RDEPENDS
just like in sysmobts.inc
Closes: SYS#3687
The old Geode based systems are replaced by AMD APU systems. We might
build for sysmobsc v1 and v2 but would like to be able to tune for the
better CPU.
This is fixing the QA issue on newer perf for x86 on Dora as seen
by the CI system. Drop support for ancient unsupported OE version
and force 3.10/4.9 depending on where we are.
mtd-utils-native needs to be available for do_deploy, so add the
dependency there. DEPENDS is meaningless for us so remove it too.
Use specific tasks as dependency to workaround an issue with poky
master where glibc-initial and glibc-locale would be direct deps.
Clone the recipe to deal with the different tasks. I wasn't able
to get the other tasks in place for dora.
In modern Poky the facade is gone and the data dictionary needs
to be accessed directly. This commit is catching up with it. It
was build tested on dora as well. I have not checked if it is
changing the checksums of a dora build.
Take a patch from newer version in Poky to hardcode the os to
Linux. This surfaced because of the more strict sysroot in newer
versions of Poky.
To avoid some bad surprises I am continuing to use this version
of ifupdown instead of the newer one in Poky.
The function is declared and defined as inline and gcc6 will not
emit an external visible symbol for it. Master doesn't have this
problem anymore so let's just patch it here.
Fixes:
| /usr/src/debug/osmo-bts/0.4.3+gitAUTOINC+57ee780789-r1a2ff06d20-r18.18/git/tests/sysmobts/sysmobts_test.c:207: undefined reference to `l1if_ms_pwr_ctrl'
In newer Poky the LDFLAGS are not passed through the $CC variable
anymore and we need to make sure scons is picking them up. Take an
old Gentoo patch for it.
Only sysmobts-v2 will override it, but all other machines should have
the same configuration as the sysmocom-bsc. This will fix the build of
our yocto-dora for sysmocom-idu/sysmocom-odu, where task-sysmocom-feed
pulls in task-gprscore which in turn wants to build the ggsn
configuration even on those machines where we don't actually have a ggsn
so far.
Yocto master has switched to use python3 and this means all of
our bbclasses must work with it. The cmp function has been removed
and the closest is this dropin routine. Start to use it.
which (at least for owhw-v2) fixes the automatic discovery of the
bootstate backend EEPROM. I suspect it should now also work without
the hardc-de-layout-values.patch on sysmobts-v2 and sysmocom-odu, but
that remains to be tested (and thus the patches remain).
UBL is setting up the flash timings (A1CR) and so far U-Boot
was overwriting it with a timing for the EVB development board
of TI. Let UBL define ECC/ChipSelect and the A1CR timings.
This might now cause different kind of flash issues because the
per chip timings might be "wrong". This is why this commit should
needs to stay in testing a bit longer. We should use this commit
on RevC, D, E and F hardware ourselves a bit.
I didn't know that u-boot was creating a package and installing
the bin into /boot. The detection of the file seems to have
changed and a new QA error comes up.
ERROR: u-boot-v2011.12+gitAUTOINC+f6453a3911-r0 do_package: QA Issue: split_and_strip_files: 'file /home/oebuilds/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/sysmobts_v2-poky-linux-gnueabi/u-boot/v2011.12+gitAUTOINC+f6453a3911-r0/package/boot/u-boot-sysmobts-v2-v2011.12+gitAUTOINC+f6453a3911-r0' failed [split-strip]
This seems to have been introduced by changing the LC_ALL to
en_US.UTF-8. I have started a dialogue with upstream development
but as we do not need a u-boot package, let's just remove the
files.
ERROR: image-rauc-ubi-1.0-r0 do_populate_lic: QA Issue: image-rauc-ubi: Recipe file does not have license file information (LIC_FILES_CHKSUM) [license-checksum]
This glib-2.0 version was required by rauc and should have been
placed in the recipes-extra (or recipes-fixes) directory.
Yocto master has imported gobject-introspecition and this requires
a newer version of glib-2.0. For Yocto master this recipe has
replaced the newer one. By moving it to the yocto-dora directory
we continue to use the old version on dora and the default version
on master.
Disabling the new "binfmt" doesn't work and breaks the build. I have
sent an email to the mailinglist and this might be fixed but at the
same time binfmt is split into a new package anyway. At the same time
we should enable some items we have now switched off. Once we start
to use/stabilize this build we need to check what we need and what the
cost is.
Yocto is now using iproute2 4.4 and the tools we packaged into
the main package are now available as extra packages and we can
just drop our extension for master.
libexecdir is now a dedicated directory and empty in our ntpd
build. Avoid QA issue of an empty directory not belonging to
anyone. Clean it if it is empty
Exception: OSError: [Errno 36] File name too long: '/home/oebuilds/jenkins/workspace/Yocto-Master/label/OE/build/tmp/deploy/sources/allarch-poky-linux/Firmware-AbilisFirmware-agereFirmware-amd-ucodeFirmware-atheros_firmwareFirmware-broadcom_bcm43xxFirmware-ca0132Firmware-chelsio_firmwareFirmware-cw1200Firmware-dib0700Firmware-ene_firmwareFirmware-fw_sst_0f28Firmware-go7007Firmware-i2400mFirmware-ibt_firmwareFirmware-it913xFirmware-iwlwifi_firmwareFirmware-IntcSST2Firmware-MarvellFirmware-mwl8335Firmware-myri10ge_firmwareFirmware-OLPCFirmware-phanfwFirmware-qat_dh895xcc_firmwareFirmware-qla2xxxFirmware-r8a779x_usb3Firmware-radeonFirmware-ralink_a_mediatek_company_firmwareFirmware-ralink-firmwareFirmware-rtlwifi_firmwareFirmware-tda7706-firmwareFirmware-ti-connectivityFirmware-ueagle-atm4-firmwareFirmware-via_vt6656Firmware-wl1251Firmware-xc4000Firmware-xc5000Firmware-xc5000cFirmware-sianoFirmware-qualcommAthos_ar3kFirmware-qualcommAthos_ath10k'
Our initramfs images are supposed to be small and don't have a
/etc/opkg folder so attempting to put feed config in there will
fail. Reset the FEED_URIS that come from our local.conf.
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.
* 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.
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>
[hfreyther: keep udev out of the dependencies]
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>
Journald being the typical GNOME application is leaking memory left
and right. Let's backport some of the patches that were done in
later versions.
Fixes: SYS#1843
* 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.
The distro is included after the machine so we can not rely
on the DISTRO_VERSION here. Use the AVAILTUNES and see if the
core2-32 is listed and then pick it.
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.
Depending on the upstream version (dora or not) we need to
use either core2 or core2-32. Use a python block expression
to pick this depending on the distro version.
E.g. when using musl and trying to build the smallest possible
rootfs. Existing builds should not start to use these flags as
they would be likely to force a big rebuild.
While copying one build to a new directory we inherit most of
the config but it is better to collect this in a single place
so external contributors build with the same options we use.
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.
By using initramfs for the rescue we occupy 8mb + ~3mb for the
kernel and can reduce the size of that slot. With glibc it is
difficult to reduce this even further. Let's see if a uclibc
build can help us
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.
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>
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
The partition layout needed for rauc is different from the one created
by the existing installer (based on the live image).
An initramfs-framework module for installation to the sysmocom-idu is
added. It is included in a corresponding initramfs image for use on an
USB memory stick.
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).
We don't use any binary only components and can avoid the performance
penalty.
[hfreyther: The ODU build had changed the tune through
the local.conf already]
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=).
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.
- 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]
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.
meta/conf/machine/include/ia32-base.inc:13 (ext3 cpio.gz live)
forces the above image formats that are not relevant to us at
all. Found and done by Jan.
The initramfs-framework from oe-core performs an endless loop of "sleep
3600" when fatal() is called. We need to reboot instead.
Signed-off-by: Jan Luebbe <jluebbe@debian.org>
* 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.
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."
Somehow master and dora generate different checksums for the
same file. Use a different file and start in the "COPYRIGHT AND
LICENSE" and hope it is stable across these two files.
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
emit something:
#use JSON::XS;
use JSON;
my %rec_hash = ('a' => 1, 'b' => 2, 'c' => 3, 'd' => 4, 'e' => 5);
my $json = encode_json \%rec_hash;
print "$json\n";
Besides DBI we need the JSON module. As far as I can see
JSON can use JSON:XS as a fast encoder/decoder. This is
why both libraries need to be provided.
We need DBI and the sqlite3 backend support for a small
monitoring application. Make it available. The files were
taken from meta-perl as of yesterday.
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
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]
Fixes: SYS#1535
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.
Related: SYS#659
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.
Related: SYS#659
Similar to the T-ODU we would like to keep a persistent log.
This commit is completely untested, rushed and not the final
one (/etc/default/volatiles/00_core most likely needs patching
and we want to limit the size of the log as well).
Related: SYS#659
* 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)
linux-sysmocom_git.bb is used for the BTS, BSC and IDU. Let's
really use 3.10.76 (from 3.10.50 just rebased and not tested
on the device yet). This should fix the Yocto-Master build
tonight.
* the oe udhcpc calls /usr/share/udhcpc/default.script which
calls run-parts -a "$1" /etc/udhcpc.d, so we can install
our script as 60ntp
* using /etc/default/udhcpc-ntp to have the possibility
to disable it on the target, its enabled per default
Related: SYS#1180
9610e792ffde7fb2599d19ca6d2a03230f2043c6 can not be found
in the linux-3.10.76 branch. Just avoid this branch game.
ERROR: Fetcher failure: Unable to find revision 9610e792ffde7fb2599d19ca6d2a03230f2043c6 in branch linux-3.10.76 even from upstream
ERROR: Function failed: Fetcher failure for URL: 'git://git.sysmocom.de/sysmo-bts/linux.git;protocol=git;branch=linux-3.10.76'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/sysmobts_v2-poky-linux-gnueabi/linux-sysmocom/3.10.76+gitAUTOINC+9610e792ff-r43/temp/log.do_fetch.16350
NOTE: recipe linux-sysmocom-3.10.76+gitAUTOINC+9610e792ff-r43: task do_fetch: Failed
ERROR: Task 126 (/home/builder/jenkins/workspace/Yocto-Master/label/OE/meta-sysmocom-bsp/recipes-bsp/linux/linux-sysmocom_git.bb, do_fetch) failed with exit code '1
pkg.m4 has been packaged in the main package for a long
while. We certainly don't need this in master anymore.
ERROR: No recipes available for:
/ws/meta-sysmocom-bsp/yocto-master/pkgconfig_0.28.bbappend
It seems like the kernel/package/upgrade/... proceess doesn't deal well
with the fact that some options used to be modules, which are now
built-in. Let's keep it as modules for the time being.
this enables conntrack events, ipset, ebtables, tc
scheduler/classifiers/ematches and much more.
it also disables the ATM code for which I don't think we have any use
case.
* we are the authoritative DHCP server for all local networks
* filter bogus windows DNS queries
* don't respect local resolv.conf (pointing to localhost)
* increase cache size to 1000 entries
Create the /run/network directory for all of our systems. The
proper way with tmpfiles.d ends with a depedency mess that has
no point in being debugged.
My local build hasn't completed yet but we need to rush. Let the
CI test this change and we will see.
Related: SYS#1514
It looks like on my tests with the sysmobts I was saved by
busybox-ifplogd executing ifup again. I couldn't figure out
the dependencies between the LSB networking service and the
tmpfiles.d interaction. So instead of winning a beauty contest
we will need to create the directory by hand.
Cause: SYS#1514
Revert "ifupdown: Package the new file as well"
This reverts commit 15dc869cda.
Revert "ifupdown: Try the workdir for the files we copied"
This reverts commit 1ef790672e.
Revert "ifupdown: Create /run/network through a tmpfiles.d"
This reverts commit e0c7f3c621.
This way the ifupdown application will not only work
for the IDU/ODU but the BTS, BSC and any other machine
we want to build.
(untested OE modification)
- the git version was choosen because it has
some fixes for newer python versions
- test where done with the test file from the github
repository and some unixsocket tests failed
Related: SYS#1082
To be able to talk to the equipment we need to set a route
after the link is up. Assume that no other (e.g. 3G) equipment
is using the same IPv4 address range.
Message-ID: 55279904.9020802@sysmocom.de
As pointed out by Harald the PR is lower than the package
that is already on the device. Bump it to 6 then.
Current:
opkg list_installed | grep ntp
ntp - 4.2.8p1-r5.0
ntp-tickadj - 4.2.8p1-r5.0
ntpdate - 4.2.8p1-r5.0
Import ntp 4.2.8 from meta-networking. Our version has some weird
dependency issues that create build breakages and more.
Remove the pps-tools dependency compared to meta-networking and
leave the ntp.conf as doneby Harald (e.g. drift on /etc and not
in /var...). Now I have not verified the upgrade path but I sadly
merged testing to stable when the ntp changes were comitted on
monday. This means I can't easily test the upgrade.
This new version of ntp has quite a number of changes, e.g.
certain utilities requiring perl, and some programs are now in
/usr/sbin rather than /usr/bin.
The sources are not using autotools and the
build breaks.
ERROR: Function failed: do_install (log file is located at /home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/armv5te-poky-linux-gnueabi/i2c-tools/3.1.1-r0/temp/log.do_install.10782)
ERROR: Logfile of failure stored in: /home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/armv5te-poky-linux-gnueabi/i2c-tools/3.1.1-r0/temp/log.do_install.10782
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
| NOTE: make -j 2 DESTDIR=/home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/armv5te-poky-linux-gnueabi/i2c-tools/3.1.1-r0/image install
| make: *** No rule to make target `install'. Stop.
| ERROR: oe_runmake failed
| WARNING: /home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/armv5te-poky-linux-gnueabi/i2c-tools/3.1.1-r0/temp/run.do_install.10782:1 exit 1 from
| exit 1
| ERROR: Function failed: do_install (log file is located at /home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/armv5te-poky-linux-gnueabi/i2c-tools/3.1.1-r0/temp/log.do_install.10782)
NOTE: recipe i2c-tools-3.1.1-r0: task do_install: Failed
In yocto versions before dizzy/master the build was done
in the source directory and when configure was executed
twice in the same directory we would have a build failure
due the symlink already existing. Simply assume that if
the ln fails the link is already there.
Out of disk space situations are handled more early by
OE and missing files will be found by configure.
In dizzy/master OE will clean the build directory before
calling configure so the issue does not apply there.
Fixes: SYS#1170
This is a late fall-out of the priority changes done by
Henning. This recipe is not using autotools and doesn't
support src != build dir builds. So let's not use the
autotools class but simply invoke install ourselves. Let's
lower the default preference so the recipe from yocto master
is picked as well.
ERROR: Function failed: do_install (log file is located at /home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/all-poky-linux/ca-certificates/20120623-r0/temp/log.do_install.16890)
ERROR: Logfile of failure stored in: /home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/all-poky-linux/ca-certificates/20120623-r0/temp/log.do_install.16890
Log data follows:
| DEBUG: SITE files ['endian-little', 'bit-32', 'common-linux', 'common-glibc', 'allarch-linux', 'common']
| DEBUG: Executing shell function do_install
| NOTE: make -j 2 DESTDIR=/home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/all-poky-linux/ca-certificates/20120623-r0/image install
| make: *** No rule to make target `install'. Stop.
| ERROR: oe_runmake failed
| WARNING: /home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/all-poky-linux/ca-certificates/20120623-r0/temp/run.do_install.16890:1 exit 1 from
| exit 1
| ERROR: Function failed: do_install (log file is located at /home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/all-poky-linux/ca-certificates/20120623-r0/temp/log.do_install.16890)
NOTE: recipe ca-certificates-20120623-r0: task do_install: Failed
ERROR: Task 3639 (/home/builder/jenkins/workspace/Yocto-Master/label/OE/meta-sysmocom-bsp/recipes-extra/ca-certificates/ca-certificates_20120623.bb, do_install) failed with exit code '1'
A lease bound/renewal could lead to the removal of a default
route set by pppd. Apply the same "dev $interface" filter that
would be used when using the "route" command.
Fixes: SYS#1163
The IDU is powerful enough to run the journald. This gives us
some convenienance to have additional output from our services
and we can query them at a later point in time.
This will only be useful for systems that are re-installed
from scratch.
Fixes: SYS#892
UUCP (cu, uux, uu*) attempts to create locks in /run/lock and it
fails. It fails because the current permission of the directory is
0755 but the binary is owned by uucp:root. Modify the legacy.conf
and change the permission to 0775.
I edited the config through make menuconfig and then used
savedefconfig but the diff from our config to a minimal
defconfig is too big. So I enabled the temp sensors and i2c
by hand.
Fixes: SYS#1148
The current 1:0.1+git1+019d2535b6-r9.2 is considered to be older
than the new gpsdate_0.1+git0+2326eee789-r10 file. Change the
PE to benefit from an upgrade.
The ODU has the GPSD for GNSS/GPS listening on a different
port. In hindsight this was a stupid decision but one we can
only fix once we move to generating the config of the system
at boot time.
Fixes: SYS#906
In case the port is not in a forwarding state.. don't just
give up but background and move on. This appears to be needed
for the odu to acquire a lease when STP is used.
For the V-ODU we want to have vlan support as well. This requires
to use the debian ifupdown which means we need a script that creates
/run/network early enough.
The name of the config file was changed and so far
I was hesitant to upgrade the MLO. I think the change
in EEPROM applies to the MLO as well so we should
upgrade it. It has neither been build tested nor tested
on a device.
On eth1 we should also use a network from the 172.16 block rather than
the 10.23 that we used on the sysmoBSC
Also, we now use 172.16.4.0/23 natively on the bridged onboard network,
this is a temporary measure so existing JBs will still connect and get
an IP address before their software is updated to use VLAN6. After they
(and all APs, BTSs, etc.) have migrated, the 172.16.4.0/23 can be
removed.
For systemd and the Debian ifupdown application we need to
have the /run/network directory. The debian init file is
creating it on the fly and we should do the same for now.
networking.service - LSB: Raise network interfaces.
Loaded: loaded (/etc/init.d/networking)
Active: failed (Result: exit-code) since Fri 2015-02-13 17:59:17 UTC; 43s ago
Process: 54 ExecStart=/etc/init.d/networking start (code=exited, status=1/FAILURE)
Feb 13 18:04:47 sysmocom-idu networking[54]: ifup: failed to open lockfile /run
/network/.ifstate.lock: No such file or directory
The creation of /run/network occurs way too late. So we need
to look for another solution.
This reverts commit 86dda7481f.
* DHCP range for 'vlan6' onboard network 172.16.2.0/23
* DHCP range for 'native' onboard network 172.16.4.0/23
* DHCP range for 'admin' port eth1 172.16.6.0/24
* domain name vessel.sob.sysmocom.de
* listen on all interfaces, not just one
* allow admin to specify static leases (ODU) in /etc/dnsmasq.dhcp-hosts
$ ifup br0.6
would go throup _none_up of links.defn and never call the
set_environ for any of the files. Check for environ being
null and then call the set_environ function to initialize
the PATH. This is changing the semantic to allow the iface,
mode and phase to be NULL. I tried to add proper null checks
--exit-on-error is not supported by the busybox run-parts
and the easiest way is to make the ignore-errors option
the default.
I didn't test the change on the device but is looks sound.
* needed to copy over the oe-core kernel-module classes
and modify them because there was no other way to use them and
name the packages kernel-module-backports
Related: SYS#850
This way we can manage bridges and vlans without additional
hacks. This package shouldn't clash with busybox so I need
to install all files with a ${BPN} suffix and then use the
update-alternatives to create the symlinks. The last two parts
were not tested/verified yet.
Ever since the priority of this layer was raised we shadow
some recipes of the default yocto. Now that we don't need
to target edison, remove some of the legacy work.
* the license in README has a new checksum, it now clarifies
to GPLv2
* bump the layer priority otherwise we could not use the latest version,
because the yocto layers have a higher priority
Related: SYS#732
This means that currently only Yocto Dora and Yocto Master are
being targeted. The amount of maintenance to get it to work on
Edison again is too high and it is better to focus on a systemd
only world. Remove the symlinks for yocto-edison.
A quick look and some notes from henning pointed me to wget
which is in the default layers, the sysmobts-2050 which is now
handle dby sysmobts and some older notes that are unlikely
to be addressed.
Okay "make modules" will lead to the kernel.release file
being re-created. So kernel.bbclass of Yocto master needs
to be fixed.
This reverts commit 3cdbc49cbb.
Somehow the do_shared_workdir tries to access a file that
should be created by do_configure but isn't present then.
Add these items to see what happens during the build.
Now reading the command it should probably be add.nwp or
rem.wp but so is life. We can add an alias for add.nwp in a
future version. The boot, recovery and fwup command have been
changed to issue nand rem.nwp before touching the flash.
We want to use backported modules this means we need to make
some thing a module for it to work. Take Daniel's .config file,
run make savedefconfig and update our defconfig.
Related: SYS#850
* The upstream sysvinit file looks good
* We are using systemd service files anyway
* The 2014.63 version doesn't exist and there is no
point in renaming the file.
The sysmobts-mgr is now linking to libgps. This means we need to
DEPEND on gpsd to have this library available. The tracking build
for both dora and master is broken due this.
This addresses the following warning of OpenVPN:
WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Go back to have our own do_configure. The kernel.bbclass would
execute "oldnoconfig" where we simply executed "oldconfig". Keep
on using our old way (for the legacy of it). E.g. with the question
how we ended up having SMP enabled in the BSC build this might
be the answer.
OE-Core seems to unpack the kernel sources into another
directory now (e.g. to share the sources with builds for
modules). Use the kernel.bbclass kernel_do_configure and
copy the .config to the build directory.
The kernel is now built in a dedicated build directory.
We actually only use the PMIC (TPS65910) RTC in the hardware,
and not the AM335x RTC. Having a driver for a hardware that doesn't
receive actual backup voltage doesn't make sense.
The odu-gpiotool is a small script created by roh to selectively reset
individual peripherals of the system by the administrator. It originates
from ticket https://projects.sysmocom.de/ortelius/issues/655
We use the new sysfs file to obtain the board version number and
configure the port swapping accordingly. If the board_version sysfs
attribute is not present, we default to v2.
We also integrate resetting the hub chip from within this tool right
befeore writing the new register values via I2C.
[hfreyther: We assume that the user might install OpenVPN with
a different priority but that it will always be available in the
runlevel two (e.g. even if the user changed the default runlevel)]
Related: SYS#517
Similiae to the layer code we simplify the machine include to work
for all versions of a 1.5 release. Poky 1.5.4 has been released and
we don't want to continue to play this game.
I have no idea who creates the /run/openvpn directory on Debian.
The path is not in a tmpfiles.d and I don't see the generator
creating it or the service file indicating that it needs to be
created. Place the file with openvpn.NAME.status into the /run
directory which appears to work on the device.
We want to use systemd for managing the lifetime of OpenVPN. Take
the debian generator (which should work with busybox ash) and the
openvpn.service (to inhibit the sysvinit script) and the target
file and install it.
On systems that have ran "update-rc.d openvpn defaults" one need
to manually execute a systemctl enable openvpn.service. This is
not done through a post-inst script and I am not sure if we should
do it. This means there is a danger of ending with a unit that
doesn't start OpenVPN automatically after upgrade!
The scripts/packages have not been tested on a device yet.
We should use a more recent version of the OpenVPN client. Import
it from the meta-networking layer like we did before. The sysvinit
script has just minor whitespace differences and wasn't imported.
We need to test opkg upgrades of OpenVPN through the VPN. We don't
want to kill the tunnel on such upgrade.
One might need to erase the environment but with a default
environment barebox will now send a LLDP during boot up. This
way we can see if a device is on a local link or not.
Fixes: SYS#488
* split out rtl-nic firmware from the big
linux-firmware package
[hfreyther: For whatever reasons the NIC works without
additional firmware as well. I couldn't see in the driver
source when that is the case and which features are missing]
Fixes: SYS#732
[hfreyther: I removed the MACHINE_ESSENTIAL_EXTRA_RDEPENDS as applications
that use the symlinks should rdepend on the package]
[hfreyther: Changed mismatch of tabs/spaces]
We want to enable the watchdog in the bootloader already and
for this to be failsafe we need to have a kernel that can boot
and get ethernet without any additional modules. Now systemd
would not be able to trigger the watchdog and the system would
reboot within 60 seconds. I am not sure how the kernel upgrade
will go and we need to try this.
Related: SYS#374
We would leak all the results for all the scans. At some point in
time the kernel OOM would kick-in and kill the process. Enable
building with -ggdb3 for debug symbols and remmeber the old list
head so we can free it.
==32240== 756 bytes in 3 blocks are definitely lost in loss record 7 of 8
==32240== at 0x40291CC: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==32240== by 0x804BCF5: iw_process_scanning_token (iwlib.c:3059)
==32240== by 0x804BCF5: iw_process_scan (iwlib.c:3255)
==32240== by 0x804BEAF: iw_scan (iwlib.c:3310)
==32240== by 0x8048FD8: scan_wifi (wifi2udp.c:72)
==32240== by 0x8048DB2: main (wifi2udp.c:143)
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.
We need a jffs2/ubi depending on the age of the hardware and
maybe a tar.bz2 so we can easily inspect an image without
playing with mtdram. We almost never need a ubifs and certainly
not a cpio.
The DISTRO_FEATURES_INITMAN variable has been removed, use
VIRTUAL-RUNTIME_init_manager which is still present. We have
already defined the later in our poky builds
systemd-compat-units does not install any files anymore and
the machineid and other scripts are gone. We want to continue
to install the alignment file though.
This has not been tested on dora systemd yet.
In dora there is no autotools-brokensep bbclass. So let's just
set the build directory to the source directory ourselves. I have
not built the package for dora though/
Poky dizzy is more strict with -I/usr/include and the old
tcpdump could pick-up "/usr/bin/pcap-config" from the host
and fail. Just upgrade to a newer version of tcpdump and be
done with it.
* 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".