Am 01.12.2014 um 18:08 schrieb Christoph Anton Mitterer: > On Mon, 2014-12-01 at 18:00 +0100, Michael Biebl wrote: >> Very likely, yes. If you use DHCP, it can easily take a few seconds for >> your network to be configured. >> And now that /etc/init.d/networking both handles allow-hotplug and auto >> interfaces and blocks for ifup to complete for those interfaces, the >> delay during boot is kinda expected. > > So can we keep the other fix as it is? I mean this will just cause > another stupid systemd-is-responsible-and-it-sucks hatred storm by > people... :(
Not quite sure what you mean with "other fix"? Can you elaborate? You can't eat a cake and have it too. Either we wait blockingly (and wait actually means, well, delaying your boot process and making it slower) for ifup to complete during boot as workaround for broken software which doesn't deal with dynamic network changes and requires $network, or we don't blockingly wait and cause that other software to break. For jessie we decided to take that boot delay hit in exchange for supporting $network requiring software. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
