On 07.12.2010 23:44, Michael Biebl wrote: > Could you please clarify what exactly happened? Was this only temporary > immediately after the upgrade? Is the problem reproducible after a upgrade?
Reproducible after a reboot, I meant. >> One approach would be for for /usr/lib/NetworkManager/ifblacklist_migrate.sh >> to convert stanzas containing any of these lines which d-i can include: >> >> wireless-mode managed >> wireless-essid * >> wireless-key1 * >> hostname * > > Are you suggesting to create a keyfile connection based on the configuration > from /etc/network/interfaces? > > Currently we don't do any conversion at all. We simply comment out any dhcp > iface configuration without any additional option. Doing a fully automated conversion would probably not be that easy and I'm not convinced it would be a good idea anyways. And we can't simply comment out entries like the above without risking to lose network connection. > If you install a new system using d-i and a /e/n/i configuration like your's > is > created, the interface will be managed by ifupdown and not network-manager. > > Or are you suggesting that NM still tries to take over the interface even if > is > configured in /e/n/i? Let me be more clear here: I fail to see the problem. Where do you think is network-manager not behaving as expected? Isn't this more a d-i problem, that it shouldn't write any /e/n/i configuration at all if network-manager is being installed? Trying to fix up such setups later in network-manager is brittle and we only do it in the most common and simplest case. Michael -- 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
