Bug#806949: ifupdown: some tweaks to networking.service

[Martin Pitt]

Hello,

Michael Biebl [2015-12-03 21:38 +0100]:
> >> Yes. The only problem though is that it requires the admin to correctly
> >> specify which interfaces are "auto" and which are "hotplug", because
> >> ifupdown cannot really figure that out itself. And there might be some
> >> cases where a virtual interface depends on one or more hotpluggable
> >> ones.
> 
> I actually think this ifupdown-wait-online service should block for
> allow-hotplug devices as well.

But then we must not use that from networking.service or anywhere else
from the boot sequence. The whole point of "allow-hotplug" is that
these devices may not be present at boot (USB devices).

> Some time ago, I hacked together a little PoC [1].

Indeed, this would be nice to integrate, and it's much more elegant
than the shell polling hack that we have in Ubuntu. Guus, would you
consider adopting this, so that we have a "wait-online" tool for all
three of ifupdown, NM, and networkd?

Thanks,

Martin


-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151204/58dc2fed/attachment-0002.sig>