On Mon, Jul 18, 2016 at 09:42:41PM +1000, Russell Stuart wrote: > My laptop stops while the all interfaces listed in /etc/network/interfaces > are configured. This isn't necessary. [...]
It is not necessary in your case. Other people have different
requirements. Also, not everything has correct dependencies. Ifupdown
errs on the safe side by scheduling itself before network.target.
> The attached patch splits networking.service into
> "networking-lo.service", which must happen before network.target, and
> "networking-all.service", which must happen before network-online.
The loopback device is actually already brought up by systemd very early
in the boot process, so there is no need for ifupdown to do this anymore
when you're using systemd.
Ifupdown is erring on the safe side with auto interfaces. I'm not going
to apply this patch. This is rather something for after the next
release.
In your situation, replace "auto" with "allow-hotplug" in
/etc/network/interfaces. This will cause those interfaces to be brought
up asynchronously. Despite the name it also brings up hardwired
interfaces at boot.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <[email protected]>
signature.asc
Description: Digital signature
