I was wondering what happens if 85-ifupdown.rules is removed. I believe /etc/init.d/networking would still do its job and networking would work fine.
If a card is removed (or added) udev wouldn't care (dinamically) about the removal (or addiction), am I wrong? But, if I understood correctly how udev work, a reboot would allow udev to get the change in the interfaces. So if this is the case I believe it should not be a problem to remove 85-ifupdown.rules, I think the number of users that remove or add cards is lower than the number of those who need a static IP for wireless and however a reboot should make everything working.
However, NM 0.7 should solve the problem by allowing system wide settings.
Some questions and some considerations.
I was wondering what happens if 85-ifupdown.rules is removed. I believe /etc/init. d/networking would still do its job and networking would work fine.
If a card is removed (or added) udev wouldn't care (dinamically) about the removal (or addiction), am I wrong? But, if I understood correctly how udev work, a reboot would allow udev to get the change in the interfaces. So if this is the case I believe it should not be a problem to remove 85-ifupdown.rules, I think the number of users that remove or add cards is lower than the number of those who need a static IP for wireless and however a reboot should make everything working.
However, NM 0.7 should solve the problem by allowing system wide settings.