Am 23.11.2014 um 00:35 schrieb Christoph Anton Mitterer:
On Tue, 2014-11-11 at 20:01 +0100, Michael Biebl wrote:
Attached is a patch against /etc/init.d/networking.
While we discussed yesterday, to only run udevadm settle if there are
any auto interfaces, I changed it, to also cover
Am 23.11.2014 um 00:35 schrieb Christoph Anton Mitterer:
On Tue, 2014-11-11 at 20:01 +0100, Michael Biebl wrote:
First, it would be great if you Christop could test this patch. Both
using allow-hotplug and auto.
Done (with the v2 patch, of course). I did about 5-7 boots for each of
the two,
Hello,
On Thu, 27 Nov 2014 01:13:23 +0100
Michael Biebl bi...@debian.org wrote:
Christoph, thanks for testing and confirming that it works.
Andrew, do you have any input/further questions on patch v2?
If not, would you be willing to add it to ifupdown and upload it so it
get's into jessie?
Hey guys...
On Mon, 2014-11-10 at 04:08 +0100, Michael Biebl wrote:
But you have seen what I've wrote previously,.. that I *do* in fact also
have issues with allow-hotplug... so there most likely is something
fishy there (or in unit files of services) as well..
So is this something that
On Mon, 2014-11-10 at 04:36 +0100, Michael Biebl wrote:
To provide such a syncronisation point, i.e. having network.target and
network-online.target [1] properly hooked up, I've implemented a PoC
ifupdown-wait-online service. You can get it from [2] and enable it via
systemctl enable
Hey.
On Tue, 2014-11-11 at 20:01 +0100, Michael Biebl wrote:
We discussed this a bit more yesterday, and we came to the conclusion,
that for jessie, it's probably the simplest solution, if we explicitly
call udevadm settle in /etc/init.d/networking before it ifup's any
devices.
A udevadm
Am 10.11.2014 um 03:40 schrieb Michael Biebl:
My suggestion would be, to make ifup -a wait for all auto interfaces
to become available with a configurable timeout (60 seconds seems like a
good compromise) after which it gives up waiting for the devices, prints
a warning and proceeds.
Am 11.11.2014 um 20:01 schrieb Michael Biebl:
Attached is a patch against /etc/init.d/networking.
While we discussed yesterday, to only run udevadm settle if there are
any auto interfaces, I changed it, to also cover allow-hotplug.
I also changed the init script to handle allow-hotplug
Control: reassign -1 ifupdown
Am 08.11.2014 um 18:20 schrieb Andrew Shadura:
reassign 766943 systemd
thanks
I don't think it's right that the bug is assigned at ifupdown.
Neither ifupdown nor its init scripts make any assumptions regarding
init system being used, so I don't see how is it
Hey Michael...
On Mon, 2014-11-10 at 03:40 +0100, Michael Biebl wrote:
allow-hotplug interfaces are configured when the actual hardware is
available.
But you have seen what I've wrote previously,.. that I *do* in fact also
have issues with allow-hotplug... so there most likely is something
Am 10.11.2014 um 04:02 schrieb Christoph Anton Mitterer:
Hey Michael...
On Mon, 2014-11-10 at 03:40 +0100, Michael Biebl wrote:
allow-hotplug interfaces are configured when the actual hardware is
available.
But you have seen what I've wrote previously,.. that I *do* in fact also
have
Am 10.11.2014 um 04:08 schrieb Michael Biebl:
Am 10.11.2014 um 04:02 schrieb Christoph Anton Mitterer:
Hey Michael...
On Mon, 2014-11-10 at 03:40 +0100, Michael Biebl wrote:
allow-hotplug interfaces are configured when the actual hardware is
available.
But you have seen what I've wrote
On Sat, 2014-11-08 at 18:20 +0100, Andrew Shadura wrote:
I don't think it's right that the bug is assigned at ifupdown.
Neither ifupdown nor its init scripts make any assumptions regarding
init system being used, so I don't see how is it more helpful
to have me dealing with this, but not
13 matches
Mail list logo
