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 ifup
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 somethin
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
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
> h
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
fi
Processing control commands:
> reassign -1 ifupdown
Bug #766943 [systemd] systemd: server no longer gets networking after switching
to systemd
Bug reassigned from package 'systemd' to 'ifupdown'.
Ignoring request to alter found versions of bug #766943 to the same values
previously set
Ignoring r
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 i
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 s
