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

[Michael Biebl]

Am 04.12.2015 um 09:35 schrieb 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).

In theory, I agree. In practice, the debian-installer has used
allow-hotplug for all devices since a few release cycles.

So I assume the vast majority of users has allow-hotplug in their
/e/n/i, even for "internal" devices (onboard, PCI, etc).


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151204/74ec8275/attachment-0002.sig>