Package: ifupdown Version: 0.7.48.1 Severity: normal Hi,
the udev package ships a udev rule [1], which runs ifup $INTERFACE via the net.agent helper. This seems to create a race with the networking SysV init script which runs also runs ifup for hotplugged interfaces in ifup_hotplug(). Is there a need to ifup allow=hotplug interfaces from within the networking init script, seeing that net.aget / 80-networking.rules already cover hotplugged interfaces? Aside from that, I do think that it would make sense to move net.agent and 80-networking.rules from udev into ifupdown proper. What do you think? [1] /lib/udev/rules.d/80-networking.rules -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ifupdown depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53.2 ii iproute 1:3.15.0-2 ii iproute2 3.15.0-2 ii libc6 2.19-4 ii lsb-base 4.1+Debian13 Versions of packages ifupdown recommends: ii isc-dhcp-client [dhcp-client] 4.3.0+dfsg-1 Versions of packages ifupdown suggests: ii net-tools 1.60-26 ii ppp 2.4.6-2 pn rdnssd <none> -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
