[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#681834: Call for votes on network-manager, gnome



On 11 September 2012 21:32, Chris Knadle <Chris.Knadle@coredump.us> wrote:
> - There are other network managers than NM.

Of course, but only one is part of GNOME. Nothing else integrates into
GNOME Shell's top bar or System Settings (gnome-control-center). GNOME
2 was different as wicd could integrate just as well as NetworkManager
did.

> - My experience has been that NM conflicts with wicd when NM is running.

You have two network managers running on your computer and you expect
networking to not have problems?

> - Furthermore my experience has been that disabling NM via modifying the
>   init script (i.e. the "exit 0" suggestion which came up on [debian-devel],
>   or making the init script non-executble) only works until NM is upgraded,
>   whereby the init script is replaced and thus the NM daemon starts again --
>   which on Sid happens fairly regularly.
>
> - Wishlist bug #685742 [1] suggested a way to disable NM permanently via a
>   /etc/default/<package> file (like wicd comes with) but was outright
>   rejected, in favor of instead using "update-rc.d network-manager disable"
>   -- the latter of which isn't mentioned anywhere in the documentation that
>   comes with NM.

'update-rc.d network-manager disable' follows the traditional way to
deactivate system services. Trying to hack the init script is a bad
idea and using /etc/default/ is unnecessary.

It looks like you're right that NetworkManager itself doesn't come
with documentation for disabling itself but maybe it should. 'man
update-rc.d' works too though.

Jeremy


Reply to: