Raphael Hertzog wrote: > On Thu, 26 Feb 2009, Michael Biebl wrote: >> See the README.Debian regarding the new managed mode. >> >> If you want to keep your devices configured via /e/n/i but managed by NM, >> then >> use managed=true in /etc/NetworkManager/nm-system-settings.conf and don't >> forget >> to kill the running nm-system-settings instance. > > I tried to remove the entry in the interfaces file and restarted > network-manager (invoke-rc.d network-manager restart) and it didn't work. > Isn't nm-system-settings restarted at the same time ?
No, it isn't. nm-system-settings is a dbus activated service (much like nm-applet, just without GUI). >> Would it help you if I added a few lines in a NEWS.Debian? > > Definitely if you plan to break compatibility from one release to the > other. Better would be to auto-add the required setting on upgrade > so that NM continues to manage what it used to manage. It's a bit more complicated than that. With 0.7, NM can handle a lot more scenarios like it did with 0.6, e.g. it finally supports static configurations. So if I set "managed=true" for nm-system-settings, static configurations in /e/n/i, which were previously ignored by NM, are now managed by NM. That's going to change the behaviour to previous NM, one way or the other. > It probably has implications for default desktop installation as well, > they would get the status "offline" back from NM, which is not really > desirable as you know, just because NM would refuse to manage the default > DHCP connection created by d-i. Yeah, I think I'm leaning towards enabling "managed=true" by default. There are still some problems with that though, (like the device being brought up twice during boot, first by ifupdown and second by NM). Cheers, 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
