On Fri, 2013-06-21 at 13:17 +0200, Florian Weimer wrote: > On 06/20/2013 09:13 PM, Dan Williams wrote: > > nmcli doesn't work unless NM is running, since it talks to NM to do > > stuff, so it would be incompatible with NM setting things up and > > quitting. > > It could spawn NetworkManager as a subprocess and use the peer-to-peer > D-Bus protocol to talk to it. I think quite a few other programs do > things this way. True. NM git master (F20) has done the peer-to-peer thing for a couple months actually. But we've previously not allowed NM to auto-spawn for a number of good reasons, mostly because starting NM can touch stuff that you may not want touched. We're hoping to change that by the F20 timeframe, so we could revisit this. > On the other hand, having NetworkManager available all the time enables > things like management tools to use its API to query system status, > instead of guessing it from kernel information and heuristic analysis of > some files under /etc. Exactly. And that's why we want to enhance NetworkManager to make people *want* to use it instead of turning it off. Dan -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
