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)
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.
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.
$ 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.
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.