As for what creates the "Before=network.target" for networking.service (aka /etc/init.d/networking): this is defined in /etc/insserv.conf.
> We should definitely not be blocking network.target indefinitely on boot waiting for the results of /etc/init.d/networking. Agreed. Conceptually we should keep the Before= so that on shutdown networking.service gets stopped after every service which provides something on the network (and thus can shut down cleanly), but on boot it's fine to asynchronously do the ifup in the background. However, I cannot actually reproduce this on the current devel-proposed image? I booted with "-net nic,model=virtio -net none" to simulate an unconnected ethernet port, and the only "hanging" job that I get is [email protected] (expectedly). network.target and getty are up, but networking.service didn't even run. But it turns out this is due to bug 1440978, I'll address this first. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1425376 Title: Ubuntu Core provides no console login prompt if network is unavailable Status in Snappy Ubuntu: New Status in cloud-init package in Ubuntu: New Status in ifupdown package in Ubuntu: Fix Released Status in systemd package in Ubuntu: New Bug description: Ubuntu Core provides no console login prompt if network is unavailable. If I plug ethernet in, it boots to the login prompt fine. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy-ubuntu/+bug/1425376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
