Bug#681834: Call for votes on network-manager, gnome
On Tuesday, September 11, 2012 22:04:08, Russ Allbery wrote:
> Chris Knadle <Chris.Knadle@coredump.us> writes:
> > - 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.
>
> The correct way to disable network-manager, or any other init script in
> Debian, is:
>
> update-rc.d <script-name> disable
>
> This will be preserved on upgrades.
Yes, I caught that earlier in the thread (before replying). My point in
bringing this up is that I think the first instinct someone has is to disable
the init script -- and this suggestion came up both in this thread as well as
on [debian-devel], which only works temporarily.
> > - 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.
>
> That's understandable since it has nothing specific to do with
> network-manager; rather, it's a standard interface in Debian for any init
> script.
>
> Most of the /etc/default hacks to disable daemons predate the
> standardization of the enable/disable interface in update-rc.d, or at
> least its widespread publication.
Okay.
-- Chris
--
Chris Knadle
Chris.Knadle@coredump.us
Reply to: