I have implemented something like what I suggested in my previous comment and it seems to work. I haven't been able to test it as completely as I'd like, but my wireless network is starting correctly at boot now with the 85-ifupdown udev rule enabled.
I wrote a script that tests whether the loopback interface is up before bringing an interface up. The idea being that if lo is not up yet when a network device is added, then presumably the system is booting and /etc/init.d/networking has not been started yet (and when it is started, it will bring up the interface). If lo is up, on the other hand, then
/etc/init.d/networking has been started already and so the new interface should be brought up by the udev rule.
I'm attaching the script with this comment, save it as /etc/udev/ifup.sh (and make it executable, obviously) and then apply the patch to 85-ifupdown.rules (which I'll also upload here).
I have implemented something like what I suggested in my previous comment and it seems to work. I haven't been able to test it as completely as I'd like, but my wireless network is starting correctly at boot now with the 85-ifupdown udev rule enabled.
I wrote a script that tests whether the loopback interface is up before bringing an interface up. The idea being that if lo is not up yet when a network device is added, then presumably the system is booting and /etc/init. d/networking has not been started yet (and when it is started, it will bring up the interface). If lo is up, on the other hand, then d/networking has been started already and so the new interface should be brought up by the udev rule.
/etc/init.
I'm attaching the script with this comment, save it as /etc/udev/ifup.sh (and make it executable, obviously) and then apply the patch to 85-ifupdown.rules (which I'll also upload here).