On Fri, 27 Feb 2009, Michael Biebl wrote: > 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.
So just add managed=true for the cases where NM did manage the connection (i.e. for dhcp option-less entries) and not for the rest. > > 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). Yes, but that's already the case now. Maybe ifupdown could be smarter… but that requires coordination with his maintainer. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
