On 19.11.2012 10:11, Miguel Angel Rojas wrote: > Hi Michael, > > Thanks for the troubleshooting. I think we have several options here > (as far as I see). We can also combined some of them: > > - Modify ifupdown to be aware of networkmanager installation (as you > suggested) > - Modify networkmanager to remove/modify/backup /e/n/i interfaces managed > by it (at installation time only or automatically done after the interfaces > is managed by networkmanager - this last one is even complex?)
I'm a bit worried about that. We already do mangle /e/n/i for dhcp-only connections [1], and NM get's a lot of bad rep because of that. If we do that, we should at least pop up a debconf prompt, so users can opt-out of that process. In the past, we had to do that, because the debian-installer creates a /e/n/i configuration for basically every system. So NM was useless by default, because it did not manage the device. This confused a *lot* of people. In d-i 7, the installer will write a NM config and *no* /e/n/i config if NM is installed e.g. via the GNOME desktop task. So I'm tempted to just drop the /e/n/i mangling altogether or as said, at least put it behind a debconf prompt. > - Message in networkmanager at installation time if ifupdown is installed > (also include this information in /usr/share/doc) A simple warning on stdout would be trivial to implement. I fear, that it might go unnoticed though for many. But it certainly is an option. > - Modify networkmanager documentation ( > http://wiki.debian.org/NetworkManager#Enabling_Interface_Management) to > point out Michael suggestion to manually remove references in /e/n/i for > interfaces managed by networkmanager (if not done automatically by previous > options) The wiki should definitely be updated. Michael [1] via /usr/lib/NetworkManager/ifblacklist_migrate.sh -- 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
