'Twas brillig, and Colin Guthrie at 20/06/13 09:31 did gyre and gimble: > Now for NetworkManager itself this more or less OK. You'll be needing it > pretty much immediately on boot anyway, but what's caught me out a > little bit more is that ModemManager (0.7.991) also follows this same > pattern. > > For me this seems a little strange. Modems are not as common these days > and I don't really want to have this enabled and running on my machine > if I don't really need it. Normally I'd expect it to be bus activated if > I go the relevant menu options via one of the NM control applets etc. > > I presume that to have "bus activation by default", the only change > needed would be to change the dbus .service file for modem manager to > refer to the SystemdService via it's normal name and not via it's bus > alias? Is this the "expected" way to work.
As Jan Steffens kindly pointed out on IRC, this is already fixed... http://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=91898aa8b0bb8164b61e84ae68534c38cebb1482 I'm reassured that my logic was at least correct, but annoyed that I didn't look first before asking the question. Hey ho. Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/ _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
